Wellness aggregator

ABSTRACT

The present disclosure relates to aggregating and sharing wellness data. The wellness data can be received by a user device from any number of sensors external or internal to the user device, from a user manually entering the wellness data, or from other users or entities. The user device can securely store the wellness data on the user device and transmit the wellness data to be stored on a remote database. A user of the device can share some or all of the wellness data with friends, relatives, caregivers, healthcare providers, or the like. The user device can further display a user&#39;s wellness data in an aggregated view of different types of wellness data. Wellness data of other users can also be viewed if authorizations from those users have been received.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/599,424, filed on Jan. 16, 2015, entitled “WELLNESS AGGREGATOR”,which claims priority to U.S. Provisional Ser. No. 62/006,032, filed onMay 30, 2014, entitled “WELLNESS AGGREGATOR,” which are herebyincorporated by reference in their entireties for all purposes. Thisapplication relates to the following provisional application: U.S.Patent Application Ser. No. 62/006,031, entitled “MANAGING USERINFORMATION,” filed May 30, 2014, which is hereby incorporated byreference in its entirety. This application also relates to thefollowing non-provisional application: U.S. patent application Ser. No.14/599,425, entitled “WELLNESS AGGREGATOR,” filed Jan. 16, 2015, whichis hereby incorporated by reference in its entirety.

FIELD

The following disclosure relates generally to data management and, morespecifically, to aggregating and sharing wellness data.

BACKGROUND

Approximately 133 million Americans currently suffer from at least onechronic condition. This number is expected to rise to approximately 165million by the year 2020. As a result, the cost of healthcare in theUnited States is expected to increase dramatically. Attempts have beenmade to improve the health of individuals by providing them with toolsto monitor and track their wellness data. Wellness data can generallyinclude any type of data associated with a person's health, such astheir weight, heart rate, blood pressure, blood glucose level,medication compliance, activity level, or the like. Users can monitortheir wellness using devices, such as blood pressure cuffs, bloodglucose monitors, electrocardiograms, step counters, and the like.Software applications (e.g., Apps) associated with each of these deviceshave also been developed to allow users to track their wellness dataover time. While each application can be used to view useful informationabout a user's health, current applications are limited in their abilityto allow users to store, view, and share wellness data collected bydifferent devices.

SUMMARY

The present disclosure relates to processes for aggregating and sharingwellness data. One example process can include causing a display of anaggregated view of a plurality of types of wellness data, wherein theaggregated view comprises a plurality of partitions, each partition ofthe plurality of partitions associated with a type of the plurality oftypes of wellness data; receiving a selection of a partition of theplurality of partitions; and causing a display of an expanded view ofthe selected partition of the plurality of partitions.

Another example process can include causing, on a device, a display of aplurality of partitions, wherein each partition of the plurality ofpartitions is associated with a type of wellness data of a plurality oftypes of wellness data; in response to detecting a change in anorientation of the device, selecting a subset of the plurality ofpartitions; and causing a display of the selected subset of theplurality of partitions.

Another example process can include causing a display of a firstplurality of partitions associated with a first user, wherein eachpartition of the first plurality of partitions is associated with a typeof wellness data of the first user; and in response to receiving arequest to view a second plurality of partitions associated with asecond user, causing a display of a second plurality of partitionsassociated with a second user, wherein each partition of the secondplurality of partitions is associated with a type of wellness data ofthe second user.

Another example process can include receiving an identification of auser authorized to access a set of wellness data; in response todetecting an update to the set of wellness data, transmitting anotification to the user authorized to access the set of wellness datanotifying the user authorized to access the set of wellness data thatthe update to the set of wellness data has been detected; andtransmitting at least a portion of the set of wellness data to the userauthorized to access the set of wellness data.

Another example process can include receiving, from a first user, arequest to access wellness data associated with a second user;transmitting, to the second user, a request to authorize the first userto access the wellness data associated with the second user; and inresponse to receiving an authorization from the second user,transmitting the wellness data associated with the second user to thefirst user.

Another example process can include, at an electronic device comprisinga display: displaying, on the display, a graph comprising a firstdata-set representation of a first data set in which a first dependentvariable varies as an independent variable changes and a second data-setrepresentation of a second data set in which a second dependent variablevaries as the independent variable changes, wherein the first data-setrepresentation is associated with a first range of vertical positionswithin the graph and the second data-set representation is associatedwith a second range of vertical positions within the graph. The processcan further include detecting, at a respective location on the display,a user input; in response to detecting the user input: in accordancewith a determination that the respective location is within the firstrange of vertical positions associated with the first data-setrepresentation, displaying, on the display, an indication that the firstdata-set representation has been selected; and in accordance with adetermination that the respective location is within the second range ofvertical positions associated with the second data-set representation,displaying, on the display, an indication that the second data-setrepresentation has been selected.

Another example process can include, at an electronic device comprisinga display: while the electronic device is in a locked state: detecting arequest to display emergency information about a user of the device; andin response to detecting the request, displaying, on the display, anemergency information interface comprising emergency information aboutthe user of the device without unlocking the device.

Another example process can include, at an electronic device: receiving,from a user, information identifying a plurality of approved sources ofwellness data, wherein the information identifying the plurality ofapproved sources identifies one or more types of wellness data that areapproved to be received from the plurality of approved sources andstored in a wellness database; and receiving, from the user, informationidentifying a plurality of approved destinations of wellness data,wherein the information identifying the plurality of approveddestinations identifies one or more types of wellness data that areapproved to be accessed from the wellness database by the plurality ofapproved destinations of wellness data.

The present disclosure also relates to methods for approving sources anddestinations of wellness data with granularity. One example process caninclude receiving, from a user, information identifying a plurality ofapproved sources of wellness data, wherein the information identifyingthe plurality of approved sources identifies one or more types ofwellness data that are approved to be received from the plurality ofapproved sources and stored in a wellness database; and receiving, fromthe user, information identifying a plurality of approved destinationsof wellness data, wherein the information identifying the plurality ofapproved destinations identifies one or more types of wellness data thatare approved to be accessed from the wellness database by the pluralityof approved destinations of wellness data.

In some examples, the plurality of approved sources comprise anelectronic device or software application.

In some examples, the plurality of approved destinations comprise anelectronic device or software application.

In some examples, the plurality of approved sources are ranked amongsteach other.

In some examples, the method further includes identifying a firstwellness data entry in the wellness database that was received from afirst approved source of the plurality of approved sources, the firstwellness data entry comprising a first wellness data type and a firsttimestamp; and identifying a second wellness data entry in the wellnessdatabase that was received from a second approved source of theplurality of approved sources, the second wellness data entry comprisinga second wellness data type and a second timestamp, wherein the firstwellness data type and the second wellness data type are the same, andwherein the first timestamp is within a threshold length of time fromthe second timestamp.

In some examples, the first approved source has been identified by theuser as being preferred over the second approved source, and wherein themethod further comprises using the first wellness data entry instead ofusing the second wellness data entry.

In some examples, the first approved source has been identified by theuser as being preferred over the second approved source, and wherein themethod further comprises prioritizing the first wellness data entry overthe second wellness data entry.

In some examples, the method further includes in accordance with adetermination that the first wellness data entry is prioritized over thesecond wellness data entry, using the first wellness data entry insteadof using the second wellness data entry.

In some examples, the second approved source has been identified by theuser as being preferred over the first approved source, and wherein themethod further comprises prioritizing the second wellness data entryover the first wellness data entry.

In some examples, the method further includes in accordance with adetermination that the second wellness data entry is prioritized overthe first wellness data entry, using the second wellness data entryinstead of using the first wellness data entry.

In some examples, the method further includes displaying, on thedisplay, a plurality of categories of wellness data stored in thewellness database.

In some examples, the method further includes detecting a selection of acategory of wellness data from the displayed plurality of categories ofwellness data; and in response to detecting the selection of thecategory of wellness data, displaying, on the display, one or moresub-categories of the category of wellness data.

In some examples, the method further includes detecting a selection of asub-category from the displayed one or more sub-categories; and inresponse to detecting the selection of the sub-category, displaying, onthe display, a detailed view of the sub-category.

In some examples, the detailed view of the sub-category comprises agraph representation of the sub-category of wellness data over time anda numerical daily value of the sub-category of wellness data.

In some examples, the detailed view of the sub-category furthercomprises an input field for entering a wellness data entry, and whereinthe method further comprises receiving a wellness data entry to bestored in the wellness database that was input into the input field.

In some examples, the detailed view of the sub-category furthercomprises a textual description of the sub-category.

In some examples, the detailed view of the sub-category furthercomprises an option to view wellness data entries corresponding to thesub-category, and wherein the method further comprises displaying, onthe display, a plurality of wellness data entries corresponding to thesub-category stored in the wellness database.

In some examples, each of the plurality of wellness data entriescomprises a numerical value of the data entry, a timestamp, and anidentification of a source of the data entry.

In some examples, the detailed view of the sub-category furthercomprises an option to share wellness data, and wherein the methodfurther includes displaying, on the display, a data sharing interfacecomprising the plurality of approved sources and the plurality ofapproved destinations.

In some examples, the method further includes detecting a request toreorder the displayed plurality of approved sources; and in response todetecting the request to reorder the displayed plurality of approvedsources, reordering the displayed plurality of approved sources inaccordance with the detected request to reorder the displayed pluralityof approved sources.

In some examples, the data sharing interface further comprises optionsto add an approved destination to the plurality of approved destinationsand to remove an approved destination from the plurality of approveddestinations.

In some examples, the method further includes receiving a search query;and displaying, on the display, one or more sub-categories of theplurality of categories that match the search query, wherein thedisplayed one or more sub-categories that match the search query arecolor-coded based on their respective categories.

In some examples, the method further includes displaying, on thedisplay, a source interface comprising a list of known sources.

In some examples, the source interface further comprises a numericalindicator associated a known source of the known sources that representsa number of new types of wellness data that can be provided by the knownsource.

In some examples, the method further includes detecting a selection of aknown source from the displayed list of known sources; and in responseto detecting the selection of the known source, displaying, on thedisplay, a list of types of wellness data that the known source canprovide.

In some examples, the list of types of wellness data that the knownsource can provide comprises a selectable option for each of the typesof wellness data that the known source can provide to approve or rejectthe associated type of wellness data.

In some examples, the method further includes detecting a selection ofthe selectable option for a type of wellness data that the known sourcecan provide; and in response to detecting the selection of theselectable option, approving or rejecting the type of wellness data thatthe known source can provide in accordance with the detected selectionof the selectable option.

Devices and non-transitory computer-readable storage media forperforming these processes are also provided.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a display in accordance with some examples.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some examples.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some examples.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay in accordance with some examples.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5 illustrates a block diagram of an example system for aggregatingwellness data according to various examples.

FIG. 6 illustrates a block diagram of an example system for sharingwellness data according to various examples.

FIG. 7 illustrates an example process for authorizing and pushingwellness data to authorized other users according to various examples.

FIG. 8 illustrates an example process for authorizing users to pullwellness data according to various examples.

FIGS. 9-14 illustrate example interfaces for displaying aggregatedwellness data according to various examples.

FIG. 15 illustrates an example process for displaying aggregatedwellness data according to various examples.

FIG. 16 illustrates an example interface for displaying aggregatedwellness data according to various examples.

FIG. 17 illustrates an example process for displaying aggregatedwellness data according to various examples.

FIG. 18 illustrates an example interface for displaying aggregatedwellness data of other users according to various examples.

FIG. 19 illustrates another example interface for displaying aggregatedwellness data of other users according to various examples.

FIG. 20 illustrates an example process for displaying aggregatedwellness data of other users according to various examples.

FIGS. 21-25 illustrate example interfaces for displaying wellness ornon-wellness data according to various examples.

FIG. 26 illustrates an example process for displaying wellness ornon-wellness data according to various examples.

FIGS. 27-36 illustrate example interfaces for displaying wellness ornon-wellness data according to various examples.

FIGS. 37A and 37B illustrate an example process for managing anddisplaying wellness or non-wellness data according to various examples.

FIGS. 38-43 illustrate example interfaces for displaying emergencymedical information according to various examples.

FIG. 44 illustrates an example process for displaying emergency medicalinformation according to various examples.

FIG. 45 illustrates an example computing system for aggregating andsharing wellness data according to various examples.

FIG. 46 illustrates a functional block diagram of an electronic deviceconfigured to display wellness or non-wellness data according to variousexamples.

FIG. 47 illustrates a functional block diagram of an electronic deviceconfigured to manage and display wellness or non-wellness data accordingto various examples.

FIG. 48 illustrates a functional block diagram of an electronic deviceconfigured to display emergency medical information according to variousexamples.

DETAILED DESCRIPTION

In the following description of the disclosure and examples, referenceis made to the accompanying drawings in which it is shown by way ofillustration specific examples that can be practiced. It is to beunderstood that other examples can be practiced and structural changescan be made without departing from the scope of the disclosure.

The present disclosure relates to aggregating and sharing wellness data.The wellness data can be received by a user device from any number ofsensors external or internal to the user device, from a user manuallyentering the wellness data, or from other users or entities. The userdevice can securely store the wellness data on the user device andtransmit the wellness data to be stored on a remote database. A user ofthe device can share some or all of the wellness data with friends,relatives, caregivers, healthcare providers, or the like. The userdevice can further display a user's wellness data in an aggregated viewof different types of wellness data. For example, the aggregated viewcan include a set of partitions, where each partition corresponds to adifferent type of wellness data. Wellness data of other users can alsobe viewed if authorizations from those users have been received. In someexamples, the partitions can be displayed as having the appearance andassociated animations of a stack of cards, where each card correspondsto a different partition (and thus, a different type of wellness data).In this view of stacked cards, each card can display a partial view of aportion of its corresponding wellness data. When the user selects one ofthe cards, a first expanded view of the selected card including at leastone of first reconfigured data, additional data, or an expanded view ofthe original data can be displayed. A second expanded view of theselected card can be displayed in response to a change in theorientation of the user device. The second expanded view can include atleast one of second reconfigured data, additional data, or an expandedview of the original data can be displayed. In one example, the secondexpanded view can include a graph of the wellness data over time.

Exemplary Devices

Examples of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someexamples, the device includes portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Examples of portable multifunction devicesinclude, without limitation, the iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. Other portable electronic devices,such as laptops or tablet computers with touch-sensitive surfaces (e.g.,touch screen displays and/or touch pads), are, optionally, used. Itshould also be understood that, in some examples, the device is not aportable communications device, but is a desktop computer or atelevision with a touch-sensitive surface (e.g., a touch screen displayand/or a touch pad). In some examples, the device does not have a touchscreen display and/or a touch pad, but rather is capable of outputtingdisplay information (such as the user interfaces of the disclosure) fordisplay on a separate display device, and capable of receiving inputinformation from a separate input device having one or more inputmechanisms (such as one or more buttons, a touch screen display and/or atouch pad). In some examples, the device has a display, but is capableof receiving input information from a separate input device having oneor more input mechanisms (such as one or more buttons, a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick. Further, as described above, itshould be understood that the described electronic device, display andtouch-sensitive surface are optionally distributed amongst two or moredevices. Therefore, as used in this disclosure, information displayed onthe electronic device or by the electronic device is optionally used todescribe information outputted by the electronic device for display on aseparate display device (touch-sensitive or not). Similarly, as used inthis disclosure, input received on the electronic device (e.g., touchinput received on a touch-sensitive surface of the electronic device) isoptionally used to describe input received on a separate input device,from which the electronic device receives input information.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, a television channelbrowsing application, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Below, FIGS. 1A-1B, 2, 3, and 4A-4B provide a description of exemplarydevices for approving sources and destinations of wellness data withgranularity.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conferencing module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions, data on stores and other points ofinterest at or near a particular location, and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, speaker 111, RFcircuitry 108, text input module 134, e-mail client module 140, andbrowser module 147, online video module 155 includes instructions thatallow the user to access, browse, receive (e.g., by streaming and/ordownload), play back (e.g., on the touch screen or on an external,connected display via external port 124), send an e-mail with a link toa particular online video, and otherwise manage online videos in one ormore file formats, such as H.264. In some embodiments, instant messagingmodule 141, rather than e-mail client module 140, is used to send a linkto a particular online video. Additional description of the online videoapplication can be found in U.S. Provisional Patent Application No.60/936,562, “Portable Multifunction Device, Method, and Graphical UserInterface for Playing Online Videos,” filed Jun. 20, 2007, and U.S.patent application Ser. No. 11/968,067, “Portable Multifunction Device,Method, and Graphical User Interface for Playing Online Videos,” filedDec. 31, 2007, the contents of which are hereby incorporated byreference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100 and/or 300 (FIGS. 1 and 3). For example, an image(e.g., icon), a button, and text (e.g., hyperlink) may each constitutean affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

System Overview

FIG. 5 illustrates an example system 500 for aggregating and sharingwellness data. As mentioned above, wellness data can include, but is notlimited to, any type of data associated with a person's health, such astheir weight, heart rate, blood pressure, blood glucose level,medication compliance, activity level, or the like. System 500 can beused to collect wellness data associated with a user, store the wellnessdata, present the wellness data to the user in useful ways, andselectively share the user's wellness data with other users or entitiesbased on permissions set by the user. In addition, in some examples,system 500 can further be used to collect non-wellness data along withwellness data, correlate the non-wellness data with the wellness data,and display the non-wellness data with the wellness data.

System 500 can include one or more user devices 510 including anyelectronic device, such as a mobile phone, tablet computer, desktopcomputer, laptop computer, PDA, or the like. In some examples, userdevice 510 can include a device similar or identical to those shown inFIGS. 1A and 3 and described above. For example, user device 510 caninclude an operating system and a wellness database 511 for securelystoring wellness or non-wellness data along with associated metadata,such as the time the data was recorded, type of data, device used torecord the data, user associated with the data, and the like. Userdevice 510 can further include application programming interfaces (APIs)with access controls for storing data in the wellness database 511 andfor accessing data stored in the wellness database 511.

User device 510 can be configured to receive wellness or non-wellnessdata from various sources and can store the received data in thewellness database 511. For example, user device 510 can be configured toreceive wellness or non-wellness data from sensors 502, 504, 506, and508. These sensors can include any type of sensor capable of obtainingwellness data, such as a biometric sensor, activity tracker, or thelike. For example, sensors 502, 504, 506, and 508 can include, but arenot limited to, a scale, blood pressure cuff, blood glucose monitor,electrocardiogram, step counter, gyroscope, accelerometer, SpO2 sensor,respiration sensor, posture sensor, stress sensor, photoplethysmogram,galvanic skin response sensor, temperature sensor, asthma inhaler, orthe like. Sensors 502, 504, 506, and 508 can also include other types ofsensors, such as audio sensors, ambient light sensors, electromagneticsensors, touch sensors, capacitive sensors, and the like, for obtainingnon-wellness data, such as situational data, temporal data, personaldata, contact data, and the like data. In some examples, each sensor canbe a separate device, while, in other examples, any combination of twoor more of the sensors can be included within a single device. Forexample, the gyroscope, accelerometer, photoplethysmogram, galvanic skinresponse sensor, and temperature sensor can be included within awearable electronic device, such as a smart watch, while the scale,blood pressure cuff, blood glucose monitor, SpO2 sensor, respirationsensor, posture sensor, stress sensor, and asthma inhaler can each beseparate devices. While specific examples are provided, it should beappreciated that other sensors can be used and other combinations ofsensors can be combined into a single device.

Sensors 502, 504, 506, and 508 can be used to measure wellness ornon-wellness data continuously, intermittently, periodically, or at anyother desired frequency or interval of time. For example, sensors 502,504, 506, and 508 can be used to obtain a single measurement or multiplemeasurements over a length of time. Sensors 502, 504, 506, and 508 canbe configured to measure wellness or non-wellness data at the sameintervals of time, or can be configured to measure wellness ornon-wellness data at different intervals of time. These intervals may beset by a user or may be a default setting for each sensor. Additionally,sensors 502, 504, 506, 508 can be used to measure wellness ornon-wellness data at any time or location desired by the user. Moreover,sensors 502, 504, 506, and 508 can be used with or without thesupervision of a healthcare provider. For example, a user can usesensors 502, 504, 506, and 508 to obtain sensor measurements at homewithout the supervision of a medical professional.

In some examples, user device 510 can include software sensorapplications 513 (e.g., third party applications) associated with eachof sensors 502, 504, 506, and 508 for interfacing with the sensors toallow user device 510 to receive the wellness or non-wellness data. Inthese examples, the applications 513 can use the device's APIs to storethe wellness or non-wellness data in the wellness database 511 of userdevice 510. In some examples, the software sensor applications 513 canbe Apps and device 510 can be a smart phone, tablet computer, or thelike. It should be understood that “third party” can correspond to anentity different than the manufacturer of device 510 and/or the entitythat created and/or maintains the operating system of device 510. Inthese instances, third party applications and their correspondingsensors can communicate and function within the operating system ofdevice 510 according to a predefined device protocol associated withdevice 510.

The applications 513 can similarly use the device's APIs to access datastored in the wellness database 511. In other examples, user device 510can be configured to share one or more communication formats withsensors 502, 504, 506, and 508 to allow user device 510 to receive andinterpret the wellness or non-wellness data from the sensors. Thereceived data can then be stored in the wellness database 511 of userdevice 510.

User device 510 can further receive wellness or non-wellness data fromits own wellness or non-wellness data sensors 515, such as a GPS sensor,clock, gyroscope, accelerometer, or the like, from a user interactingwith user device 510, from another entity, such as a physician, or fromother non-sensor sources. For example, using the device's APIs, wellnessor non-wellness data can be received from applications 517 on userdevice 510, such as a clock application, a calendaring application, agaming application, an application from a healthcare provider, amessaging application, or the like. The wellness or non-wellness datafrom the applications 517 can originate from a user interacting with theapplications, a remote database (e.g., database for a medical website),a healthcare provider institution (e.g., via the institution's App), orthe like. In these examples, the usage of the application 517 (e.g., howlong you play a video game application, when you play the video game,number of times interacting with a stock application, number of timesinteracting with a social networking application, length of timeinteracting with a social networking application, etc.), usage of userdevice 510 (e.g., length of time on the phone or number of text messagessent as determined from a phone payment application, time spent browsingthe Internet as determined from the device's browser, etc.), time spentlistening to music as determined from a music or streaming radioapplication, time spent using a remote application for controlling atelevision, amount of time or money spent on shopping websites, timespent on pornographic websites (e.g., to identify addictions), weatherdata from a weather application (e.g., to determine how weather affectsa user's health), type of events occurring in the user's life asdetermined from a calendar (e.g., meetings, birthdays, holidays, etc.),interactions with certain people as determined from a contact listand/or calendar application and/or a messaging application and/or phoneof user device 510, or the like, can be received by user device 510 andstored in the wellness database 511.

In some examples, default or user-selected settings can be provided torestrict the access that at least one application (e.g., at least one ofapplications 513 and 517) on user device 510 has to the wellnessdatabase 511 of user device 510 (for both storage and retrievalpurposes) and to the sensor data generated by sensors 515 within userdevice 510 and/or sensor data generated by sensors 502, 504, 506, and508. For example, an application for tracking a user's running sessionscan be granted access to the data generated by the GPS sensor of userdevice 510, but can be prevented from accessing the user's bloodpressure data stored in the wellness database 511. In some examples, anentity other than the owner of user device 510 can set the authorizationsettings for various applications on user device 510. For example, themanufacturer of user device 510 and/or the entity that created and/ormaintains the operating system of user device 510 can evaluate theapplications to determine if they should be given access to the user'swellness data and/or sensor data generated or received by user device510. In some examples, these settings can be overridden by the user.

User device 510 can further include a display for displaying the storedwellness data or non-wellness data. A more detailed description of theinterface of the display of user device 510 is described below withrespect to FIGS. 11-17.

FIG. 6 illustrates system 600 for sharing user wellness data. Referringto FIG. 6, user server 514 can be communicatively coupled to user device510 via network 512, which can include the Internet, an intranet, or anyother wired or wireless public or private network. User device 510 canbe configured to securely transmit the aggregated wellness ornon-wellness data and associated metadata stored on the device to userserver 514 for storage in user database 516. In some examples, thewellness or non-wellness data and associated metadata can be transmittedto user server 514 for storage in user database 516 in response to anexplicit request for such a transfer by the user of device 510, while,in other examples, the wellness or non-wellness data can be synced withthe data in user database 516 continuously, periodically,intermittently, or at any desired frequency. In yet other examples, theuser's wellness or non-wellness data can be stored only on user device510 and may not be stored in an external database.

In some examples, user server 514 and user database 516 can beconfigured to securely store a user's wellness or non-wellness datausing a public/private key system that only allows the owner of thewellness or non-wellness data to decrypt the data. Additionally, thewellness or non-wellness data stored in user database 516 can be storedanonymously (e.g., without identifying and/or personal information aboutthe user, such as a legal name, username, time and location data, or thelike). In this way, other users, hackers, and the owner/operator of userdatabase 516 cannot determine the identity of the user associated withthe data stored in database 516. In some examples, a user can accesstheir wellness or non-wellness data stored in user database 516 from auser device that is different than the one used to upload the wellnessor non-wellness data to user server 514. In these instances, the usercan be required to provide login credentials to access their wellness ornon-wellness data. User server 514 can be configured to perform theauthorization process to restrict access to the data within userdatabase 516.

System 600 can further include any number of other user devices 522 and524 coupled to network 512. In some examples, user devices 522 and 524can be operated by the same user as user device 510. In these instances,the user can access their wellness or non-wellness data stored in userdatabase 516 by providing user server 514 with the appropriatecredentials. In some examples, wellness and non-wellness data can besynced between user database 516 and one or more of user device 510,522, and 524. In other examples, the user of user devices 522 and 524can be a person that is different than the user of user device 510. Inthese examples, the users of devices 522 and 524 cannot access thewellness or non-wellness data of the user of user device 510 without theauthorization of the user of user device 510. If authorization is given,wellness or non-wellness data can be shared with the users of userdevices 522 and 524. The sharing of this data will be discussed ingreater detail below with respect to FIGS. 7-8.

In some examples, any of the above described sources of wellness ornon-wellness data can be configured to measure, generate, or receivewellness or non-wellness data continuously, intermittently,periodically, or at any other desired frequency or interval of time. Assuch, the wellness or non-wellness data can similarly be stored orupdated in wellness database 511 or user database 516 continuously,intermittently, periodically, or at any other desired frequency orinterval of time. The frequencies and intervals of time used formeasuring, generating, receiving, or storing wellness or non-wellnesscan be the same or they can be different. Additionally, thesefrequencies and intervals can be default values or they can be set by auser to provide the user with wellness or non-wellness data that hasbeen updated within a desired length of time.

While not shown, it should be appreciated that many other user devicescan be coupled to user server 514 through network 512 to collect andstore wellness or non-wellness data for other users in a manner similarto that described above.

User Database

As discussed above, a user's wellness or non-wellness data can be storedin user database 516 and can be shared with other users with the owninguser's authorization. The other users can be any type of user, such as afriend, family member, caregiver, physician, social media provider, orthe like. Different types and levels of authorization can be granted forthe wellness or non-wellness data contained in wellness database 516.

In some examples, the shared wellness or non-wellness data can be pushedto the user device (e.g., user device 522 or 524) of the authorizedother user. FIG. 7 illustrates an example process 700 for authorizingand pushing wellness or non-wellness data to authorized other users. Atblock 702, an identification of an authorized other user can bereceived. This can be received by a user device (e.g., user device 510)from the user associated with the shared wellness or non-wellness data.The identification can include a username, legal name, contactinformation, or any other identifier or credential for the other user,along with a level of access, such as access to all of the wellness ornon-wellness data or a subset of the wellness or non-wellness data. Insome examples, the authorized other user can be grouped into categoriesof users (e.g., family, friends, other, etc.), where each category isassociated with a particular set of wellness data types that thoseauthorized other users are allowed to view. For example, users in thefamily category can be allowed to view all types of wellness data, whileusers in the friend category can only view activity data.

At block 704, the user's wellness or non-wellness data can be monitoredby the user's device to determine if any updates to the data have beenmade. If no update has been made, the process can repeat block 704. If,however, an addition or change to the user's wellness or non-wellnessdata has been identified, the process can proceed to block 706. In someexamples, any change to the user's wellness or non-wellness data cancause process 700 to proceed to block 706, while, in other examples,only changes to certain types of the user's wellness or non-wellnessdata can cause process 700 to proceed to block 706.

At block 706, a notification can be transmitted to one or moreauthorized other users. For example, a notification can be transmittedfrom the user's device (e.g., user device 510) to the device of theauthorized other user (e.g., user device 522 or 524). The notificationcan include a message indicating that an update has been made to theuser's wellness or non-wellness data. The process can then proceed toblock 708.

At block 708, the updated wellness or non-wellness data can betransmitted to the authorized other user. For example, the updatedwellness or non-wellness data can be transmitted from the user's device(e.g., user device 510) to the device of the authorized other user(e.g., user device 522 or 524). In some examples, this data can only betransmitted if the authorized other user indicated a desire to view theupdated wellness or non-wellness data, while, in other examples, theupdated wellness or non-wellness data can be transmitted to the userdevice of the authorized other user without receiving a request from theauthorized other user to view the data.

The pushing of wellness or non-wellness data performed using process 700can be useful in situations in which a user wants to keep a caregiver orfamily member (or other user) updated with his/her wellness ornon-wellness data. For instance, an elderly parent can grantauthorization to push his/her wellness or non-wellness data to a childto allow the child to easily monitor the elderly user's health ormedication compliance without having to constantly request thisinformation from the parent.

In other examples, a user's wellness or non-wellness data can be sharedwith other users by allowing other users to pull the wellness ornon-wellness data. FIG. 8 illustrates an example process 800 forauthorizing other users to pull wellness or non-wellness data. At block802, a request to access a particular user's wellness or non-wellnessdata can be received. The request can identify the user associated withthe requested wellness or non-wellness data and, optionally, the portionof the wellness or non-wellness data to be accessed. The identificationcan include a username, legal name, contact information, or any otheridentifier or credential for the user. The request can be received by auser device (e.g., user device 510) of the user associated with therequested data from a user device (e.g., user device 522 or 524) of therequesting user.

At block 804, a request for authorization can be transmitted to the userassociated with the requested wellness or non-wellness data. In someexamples, the request can be transmitted from the user device (e.g.,user device 522 or 524) of the requesting user to the user device (e.g.,user device 510) of the user associated with the requested data. Therequest can then be displayed to the user associated with the requesteddata by the user's device (e.g., user device 510).

At block 806, it can be determined if an authorization has been receivedfrom the user associated with the requested wellness or non-wellnessdata. The authorization can be received in any manner. For example, aprompt can be displayed to the user associated with the requested dataon their user device 510. If authorization is denied, the process canreturn to block 802. If, however, authorization is granted, the processcan proceed to block 808.

At block 808, the requested wellness or non-wellness data can betransmitted to the entity that requested access to the wellness ornon-wellness data at block 802. The requested wellness or non-wellnessdata can be transmitted from the user's device (e.g., user device 510)to the requesting entity's device (e.g., user device 522 or 524).

In some examples, if authorization to access a user's wellness ornon-wellness data is granted before a request is made at block 802,process 800 can proceed from block 802 to block 808 without performingblocks 804 or 806. For example, if a parent grants access to theirwellness or non-wellness data to their child, a request by the child forthe parent's wellness or non-wellness data can be received at block 802and the requested wellness or non-wellness data can be transmitted tothe child at block 808 without any intervening action by the parent.

The pulling of wellness or non-wellness data using process 800 can beuseful in situations where an authorized other user does not want to beconstantly updated with updates to a user's wellness or non-wellnessdata, but would like occasional access to the data. For example, aphysician may want access to a patient's medical records and wellness ornon-wellness data just prior to meeting with the patient. In thissituation, the physician can request the patient's wellness ornon-wellness data and can either receive the requested data or cause arequest to be sent to the user device 510 of the patient. In response toreceiving an authorization from the patient, the requested data can besent from user device 510 to the physician's computing device (e.g.,user device 522 or 524). In some examples, the received wellness ornon-wellness data can be added to an electronic medical record (EMR)associated with the user.

In some examples, whether using a push or pull sharing model, thewellness or non-wellness data of a user may not be permanently stored onthe user device of authorized other users. In this way, authorization tothese other users can be revoked, causing the user's wellness data to beinaccessible by the formerly authorized other users. Additionally, insome examples, reports detailing or summarizing a user's wellness ornon-wellness data can be generated. These reports can then betransmitted via email, secure transfer, or the like, to any desiredrecipient. In yet other examples, user device 510 can be configured tocommunicate some or all of the user's wellness or non-wellness data,such as medical insurance information, blood type, medical history,etc., to medical personnel using near field communication or anothercommunication protocol. This can be useful when checking in to ahospital or during medical emergencies when relevant medical data isneeded.

Aggregated Data View

As discussed above, user device 510 can be configured to aggregatewellness or non-wellness data associated with a user that was receivedfrom the user, from one or more sensors 502, 504, 506, and 508, or fromanon-sensor source. User device 510 can also be configured to displaythe user's aggregated wellness or non-wellness data in various waysusing various interfaces.

FIG. 9 illustrates one example interface 900 that can be used by userdevice 510 to display a user's aggregated wellness or non-wellness data.Interface 900 can include any number of partitions 902, 904, 906, 908,910, and 912, each containing a different type of wellness dataassociated with the user. In the aggregated view of FIG. 9, thepartitions can be used to display a partial view of a portion of thedifferent types of wellness data. In the examples shown in FIGS. 9-14,16, and 18-19, the partitions are illustrated as having the appearanceand associated animations of a stack of cards, where each cardcorresponds to a different partition (and thus, a different type ofwellness data). It should be appreciated, however, that the partitionscan be displayed in any other desired manner.

Interface 900 can include a first partition 902 displayed at the top ofthe interface that can include an identifier (e.g., name) of the user.As shown, the name “John Smith” of the user of user device 510 isdisplayed on partition 902. Interface 900 can further include button 901for viewing wellness data associated with other users. This feature isdescribed in greater detail below with respect to FIGS. 14 and 15.

Interface 900 can further include another partition 904 displayedadjacent to partition 902 such that it appears to be overlappingpartition 902 like a stacked card. This partition can include anindication of the type of wellness data contained on the partition aswell as a partial view (e.g., summary, example, or the like) of aportion the partition's wellness data. Specifically, partition 904includes the word “Weight” to indicate that the partition containsweight data associated with the user “John Smith.” Partition 904 canfurther include the most recent weight “185 lbs” of “John Smith.”

Interface 900 can further include another partition 906 displayedadjacent to partition 904 such that it appears to be overlappingpartition 904 like a stacked card. This partition can include anindication of the type of wellness data contained on the partition aswell as a partial view (e.g., summary, example, or the like) of aportion the partition's wellness data. Specifically, partition 906includes the words “Blood Sugar” to indicate that the partition containsblood sugar data associated with the user “John Smith.” Partition 906can further include the most recent blood sugar level “164 mg/dL” of“John Smith.”

Interface 900 can further include another partition 908 displayedadjacent to partition 906 such that it appears to be overlappingpartition 906 like a stacked card. This partition can include anindication of the type of wellness data contained on the partition aswell as a partial view (e.g., summary, example, or the like) of aportion the partition's wellness data. Specifically, partition 908includes the words “Blood Pressure” to indicate that the partitioncontains blood pressure data associated with the user “John Smith.”Partition 908 can further include the most recent blood pressuremeasurement “117/67 mmHg” of “John Smith.”

Interface 900 can further include another partition 910 displayedadjacent to partition 908 such that it appears to be overlappingpartition 908 like a stacked card. This partition can include anindication of the type of wellness data contained on the partition aswell as a partial view (e.g., summary, example, or the like) of aportion of the partition's wellness data. Specifically, partition 910includes the word “Activity” to indicate that the partition containsactivity data (e.g., calories burned) associated with the user “JohnSmith.” Partition 910 can further include the current daily number ofcalories burned “467 kcal” by “John Smith.”

Interface 900 can further include another partition 912 displayedadjacent to partition 910 such that it appears to be overlappingpartition 910 like a stacked card. This partition can include anindication of the type of wellness data contained on the partition aswell as a partial view (e.g., summary, example, or the like) of aportion of the partition's wellness data. Specifically, partition 912includes the words “Heart Rate” to indicate that the partition containsheart rate data associated with the user “John Smith.” Partition 912 canfurther include the most recent heart rate measurement “122 bpm” of“John Smith.” Additionally, since partition 912 is at the top of thestack of partitions, additional information 914 and/or options 916 canbe displayed on the face of the partition. In the illustrated example,the additional information includes the minimum, maximum, and restingheart rate of “John Smith” over the span of a week, which was selectedusing options 916.

The ordering of some or all of the partitions can be static or dynamic.For example, partition 902 containing the user's name can remain at thetop of the display, while the remaining partitions can be ordered basedon the time of day, how recently the wellness data associated with thepartition is updated, the frequency that the wellness data associatedwith the partition is updated, whether a notable event is approaching(e.g., medication that should be taken, a sensor measurement that shouldbe performed, etc.), or the like. The ordering can also be manuallychanged by the user. If interface 900 includes more partitions than canbe displayed on a single screen, a vertical scrolling can be performedto display the remaining partitions. Alternatively, a 3D scrolling ofthe partitions may be performed to give the appearance of flippingthrough a stack of cards.

While specific example partition types have been provided above, itshould be appreciated that partitions containing different types ofwellness data can be included within interface 900. Additionally, userscan generate customized partitions that can be used to display anydesired type of user-entered data. For example, a partition can becreated to track the medication compliance of a user. The user can enterthe time, amount, and type of medicine taken and this data can bedisplayed on the created partition. Other custom partitions fordifferent wellness data types, such as nutrition, sleep, smoking, or thelike can also be generated.

Additionally, while specific examples of partial views (e.g., summary,example, or the like) of a portion of the partitions' wellness data havebeen provided above, it should be appreciated that the partial views cansummarize or provide examples of the wellness data in different ways.For example, rather than display the most recent value of a particularwellness data type, a mean, mode, median, another single data point, orthe like of the wellness data over all or a portion of time (e.g., aweek, month, year, etc.) can be displayed on the partitions in theaggregated view. Alternatively, in other examples, a current and averagevalue can be displayed on the partitions in the aggregated view. In yetother examples, the partitions in the aggregated view can include adisplay of a current value and a goal value for the type of wellnessdata.

The partitions 902, 904, 906, 908, 910, and 912 can be selected todisplay an expanded view of the partition containing reconfigured data,additional data, or an enlarged view of the original data contained onthe partition. For example, a user can select a partition by tapping onthe desired partition displayed on a touch sensitive display, canhighlight and click on the partition using a mouse or other inputdevice, or select the desired partition using any other input means. Inresponse to a selection of a partition, user device 510 can hide thecontents of the other partitions and display the selected partition onall or most of the display of user device 510.

For example, FIG. 10 illustrates an example interface 1000 that can bedisplayed in response to a user selecting partition 904 in interface900. In interface 1000, expanded view 905 of partition 904 can bedisplayed prominently within the display of user device 510, while theremaining partitions can be animated as being collapsed off the displayinto the stack of partitions 1002 displayed at the bottom of thedisplay. In the illustrated example, expanded view 905 can includeadditional weight-related data, such as the user's weight, body massindex (BMI), and fat percentage, that were not shown in interface 900.Expanded view 905 can further include summaries of the user's weightdata, such as a sliding scale 1040 indicating the user's weight relativeto a range of weights and a graph 1041 tracking the user's weightthroughout the day, week, month, or year. Interface 1000 can furtherinclude button 1004 that can cause user device 510 to display optionsfor sharing some or all of their wellness data using any desiredcommunication medium, such as text message, email, social mediaprovider, or the like. In these examples, the wellness data can beencrypted and sent from the user device 510 directly to the user deviceof the recipient (rather than from user server 514), where the wellnessdata can be decrypted. To return to the aggregated view of partitionsshown in interface 900, the user can select (e.g., tap, click, orotherwise select) the stack of partitions 1002. It should be appreciatedthat the contents of interface 1000 and expanded view 905 are providedas examples, and that expanded view 905 can instead include any type orsummary of weight-related data.

FIG. 11 illustrates an example interface 1100 that can be displayed inresponse to a user selecting partition 906 in interface 900. Ininterface 1100, expanded view 907 of partition 906 can be displayedprominently within the display of user device 510, while the remainingpartitions can be animated as being collapsed off the display into thestack of partitions 1002 displayed at the bottom of the display. In theillustrated example, expanded view 907 can include additional bloodsugar-related data, such as the user's blood sugar and units that werenot shown in interface 900. Expanded view 907 can further includesummaries of the user's blood sugar data, such as a sliding scale 1042indicating the user's blood sugar after a meal relative to a range oftypical blood sugar level and a graph 1043 tracking the user's bloodsugar throughout the day, week, month, or year. Interface 1100 can alsoinclude button 1004, described above. To return to the aggregated viewof partitions shown in interface 900, the user can select (e.g., tap,click, or otherwise select) the stack of partitions 1002. It should beappreciated that the contents of interface 1100 and expanded view 907are provided as examples, and that expanded view 907 can instead includeany type or summary of blood sugar-related data.

FIG. 12 illustrates an example interface 1200 that can be displayed inresponse to a user selecting partition 908 in interface 900. Ininterface 1200, expanded view 909 of partition 908 can be displayedprominently within the display of user device 510, while the remainingpartitions can be animated as being collapsed off the display into thestack of partitions 1002 displayed at the bottom of the display. In theillustrated example, expanded view 909 can include additional bloodpressure-related data, such as the user's blood pressure and beats perminute (bpm) that were not shown in interface 900. Expanded view 909 canfurther include summaries of the user's blood pressure data, such as asliding scale 1044 indicating the user's blood pressure relative totypical blood pressure values and a graph 1045 tracking the user's bloodpressure throughout the day, week, month, or year. Interface 1200 canalso include button 1004, described above. To return to the aggregatedview of partitions shown in interface 900, the user can select (e.g.,tap, click, or otherwise select) the stack of partitions 1002. It shouldbe appreciated that the contents of interface 1200 and expanded view 909are provided as examples, and that expanded view 909 can instead includeany type or summary of blood pressure-related data.

FIG. 13 illustrates an example interface 1300 that can be displayed inresponse to a user selecting partition 910 in interface 900. Ininterface 1300, expanded view 911 of partition 910 can be displayedprominently within the display of user device 510, while the remainingpartitions can be animated as being collapsed off the display into thestack of partitions 1002 displayed at the bottom of the display. In theillustrated example, expanded view 911 can include additionalactivity-related data, such as the calories burned, steps taken, andmiles traveled by the user that were not shown in interface 900.Expanded view 911 can further include summaries of the user's bloodpressure data, such as a graph 1046 tracking the intensity of theiractivity throughout the day, week, month, or year, and summaries 1047showing the total time spent active, idle, and exercising. Interface1300 can also include button 1004, described above. To return to theaggregated view of partitions shown in interface 900, the user canselect (e.g., tap, click, or otherwise select) the stack of partitions1002. It should be appreciated that the contents of interface 1300 andexpanded view 911 are provided as examples, and that expanded view 911can instead include any type or summary of activity-related data.

FIG. 14 illustrates an example interface 1400 that can be displayed inresponse to a user selecting partition 912 in interface 900. Ininterface 1400, expanded view 913 of partition 912 can be displayedprominently within the display of user device 510, while the remainingpartitions can be animated as being collapsed off the display into thestack of partitions 1002 displayed at the bottom of the display. In theillustrated example, expanded view 913 can include additional heartrate-related data, such as minimum, maximum, and resting heart rate ofthe user over a day, week, month, or year. However, unlike partitions904, 906, 908, and 910, this data was previously displayed withininterface 900 since partition 912 was displayed in the aggregated viewas being located at the top of the stack of partitions. Expanded view913 can further include a summary of the user's heart rate data, such asa graph 1048 tracking the user's heart rate throughout the day, week,month, or year. Interface 1400 can also include button 1004, describedabove. To return to the aggregated view of partitions shown in interface900, the user can select (e.g., tap, click, or otherwise select) thestack of partitions 1002. It should be appreciated that the contents ofinterface 1400 and expanded view 913 are provided as examples, and thatexpanded view 913 can instead include any type or summary of heartrate-related data.

In some examples, a user's wellness data used to generate the interfacesshown in FIGS. 9-14 may have been received from one or more sensordevices and/or applications. In these examples, the wellness data of thesame type from different devices may be combined and displayed on asingle partition. For example, the weight data shown in interface 1000in FIG. 10 can be obtained from repeated measurements taken using thesame scale. Alternatively, some of the measurements could have beenobtained from one scale, while the remaining measurements could havebeen obtained from one or more different scales. As a result, somepoints in graph 1041 could have been generated using weight data fromone scale, while other points in graph 1041 could have been generatedusing weight data from one or more other scales. In another example, theactivity data shown in interface 1300 in FIG. 13 may have been obtainedfrom a single step counting device. Alternatively, the data may beaggregated from a step counting device, a first GPS-enabled watch usedto record a user's running session, and a second GPS-enabled watch usedto record a user's rowing session. In these examples, graph 1046 showingthe intensity of the user's activity can be a segmented graph generatedfrom a combination of the data obtained from the step tracking deviceand the first and second GPS-enabled watches, with each segment comingfrom one of the devices. In particular, graph 1046 can include a firstsegment 1050 generated from data from the step counting device, a secondsegment 1052 generated from data from the first GPS-enabled watch, and athird segment 1054 generated from data from the second GPS-enabledwatch. Aggregating data in this way advantageously allows a user torecord and view wellness data in a manner that does not directly tie thewellness data to a particular device or application (e.g., smartphoneapplications). While three segments are shown in FIG. 13, it should beappreciated that the segmented graph can include any number of segmentscorresponding to different sensors and/or applications.

FIG. 15 illustrates an example process 1500 for displaying wellness dataaccording to various examples. At block 1502, an aggregated view ofwellness data containing a plurality of partitions similar or identicalto partitions 902, 904, 906, 908, 910, and 912 can be displayed on auser device similar or identical to user device 510. The partitions caninclude an identifier for the type of wellness data displayed on thepartition and a partial view (e.g., summary, example, or the like) of aportion of the type of wellness data associated with the partition. Forexample, an interface similar or identical to interface 900 can bedisplayed containing various wellness data partitions 902, 904, 906,908, 910, and 912.

At block 1504, a selection of one of the displayed partitions can bereceived. The selection can be received by the user device, and can bein the form of a mouse click, tap on a touch sensitive display, or thelike. In response to a selection of the partition, an expanded view ofthe selected partition can be displayed at block 1506. The expanded viewcan include a view showing a larger portion of the selected partitionand at least one of reconfigured wellness data (e.g., a rearranged viewof the wellness data displayed on the selected partition in theaggregated view displayed at block 1502), additional wellness data(e.g., wellness data that was not previously displayed on the selectedpartition in the aggregated view displayed at block 1502), or anenlarged view of the wellness data displayed in the aggregated viewdisplayed at block 1502 (e.g., a larger view of the same wellness datadisplayed on the selected partition in the aggregated view displayed atblock 1502). Additionally, partitions that were not selected can bereduced in size or removed from the display. For example, any ofinterfaces 1000, 1100, 1200, 1300, or 1400 can be displayed in responseto a selection of partition 904, 906, 908, 910, or 912 of interface 900,respectively.

In some examples, the display presented at block 1506 can include aselectable option (e.g., button 1004) to share wellness data. In otherexamples, the display presented at block 1506 can further include aselectable option (e.g., partitions 1002) to cause the aggregated viewcontaining partitions displayed at block 1502 to again be displayed. Theprocess can then return to block 1504, where a selection of anotherpartition can be received.

FIG. 16 illustrates an example interface 1600 that can be displayed inresponse to a user rotating user device 510 to a landscape view. In thisorientation, user device 510 can display expanded views of a smallersubset of partitions than displayed in the aggregated view of interface900. For example, interface 1600 can include expanded view 1602 ofpartition 908, expanded view 1604 of partition 906, and expanded view1606 of partition 912. In the illustrated example, the expanded views ofthe partitions can include graph representations of the wellness dataover various lengths of time. This can allow a user to view thedisplayed types of wellness data and see how they change relative toeach other over time and to evaluate how a change in one type ofwellness data relates to a change (or lack thereof) in another type ofwellness data. For example, one type of wellness data that can bedisplayed can include medications taken over time. This data can becompared to a user's blood pressure and heart rate to determine if themedication is having a beneficial or detrimental effect. In someexamples, user device 510 can select the types of wellness data to bedisplayed when user device 510 is rotated into landscape orientation.The selection can be made based on predetermined combinations ofwellness data types that are often associated with each other or can bemade based on an analysis of the various types of wellness data. In thelatter example, wellness data types that are identified as potentiallybeing correlated can be displayed. Wellness data types not shown in theinitial display of interface 1600 can be viewed by scrolling through thepartitions. Additionally, the partitions can be selected to display moredetailed information in the same way as performed in interface 900.

FIG. 17 illustrates an example process 1700 for displaying wellness databased on an orientation of the device according to various examples. Atblock 1702, an aggregated view containing a plurality of partitionssimilar or identical to partitions 902, 904, 906, 908, 910, and 912 canbe displayed by a user device similar or identical to user device 510.The partitions can include an identifier for the type of wellness datadisplayed on the partition and a partial view (e.g., summary, example,or the like) of a portion the type of wellness data associated with thepartition. For example, an interface similar or identical to interface900 can be displayed containing various wellness data partitions 902,904, 906, 908, 910, and 912.

At block 1704, a change in orientation of the user device can bedetected. For example, a gyroscope and/or an accelerometer within theuser device can indicate that the orientation of the device has beenchanged from portrait to landscape. In response to a detected change inorientation by a threshold amount, the process can proceed to block1706.

At block 1706, a subset of the plurality of partitions displayed atblock 1702 can be selected for display. In some examples, the subset canbe a predetermined subset of the plurality of partitions. In otherexamples, the subset can be selected based on user-defined preferencesfor display. In yet other examples, the subset of the plurality ofpartitions can be selected based on an analysis of the wellness datasets associated with each partition to determine if any of the types ofwellness data are potentially correlated. If a potential correlation isidentified, the partitions associated with the potentially correlateddata can be selected at block 1706.

At block 1708, expanded views of the subset of partitions selected atblock 1706 can be displayed. In some examples, the identifier for thetype of wellness data displayed on the expanded view of the partitionand/or the summary, example, or other view of the type of wellness dataassociated with the partition can be different than that shown on thepartitions at block 1702. For example, the summary or example data oneach expanded view can be replaced with a graph representation of thewellness data over time, as shown in FIG. 16. In this way, relationshipsbetween the displayed types of wellness data can be observed. In someexamples, in response to detecting a change in the orientation of theuser device to a portrait orientation, the process can return to block1702.

As discussed above, in some examples, the user of user device 510 can begranted access to the wellness data of other users. In these examples,user device 510 can allow the user to view the wellness data of otherusers in a similar format as discussed above with respect to FIGS. 9-17.For example, as shown by interface 1800 in FIG. 18, to view the wellnessdata of other users, the user can laterally scroll the contents of theinterface in direction 1806 to cause a first set of partitions 1804 froma first user to be displayed in place of the second set of partitions1802 from a second user. In particular, the second set of partitions1802 for the second user can be translated off the display in thedirection 1806 of the scroll, while the first plurality of partitions1804 can be translated onto the display in the same direction 1806 butfrom the opposite side of the display. It should be appreciated thatFIG. 18 illustrates a transitional state in which partitions 1802 arebeing removed from the display and partitions 1804 are being scrolled indirection 1806 onto the display. As such, only the left side ofpartitions 1802 and the right side of partitions 1804 are visible. Aspartitions 1802 and 1804 continue to be scrolled in direction 1806, asmaller portion of partitions 1802 may be visible while a larger portionof partitions 1804 may be visible until partitions 1802 are completelyremoved from the display and partitions 1804 occupy all or most of thedisplay. While not shown, the top partition of partitions 1804 caninclude the first user's name and can be displayed as the screencontinues to be scrolled in direction 1806. This scrolling operation canbe performed any number of times (and in any direction) to scrollthrough the partitions for all users that the user of device 510 isauthorized to access.

FIG. 19 illustrates another example interface 1900 for viewing thewellness data of other users. In some examples, interface 1900 can bedisplayed in response to a selection of button 901 of interface 900. Asshown, interface 1900 can include a list of users 1902, 1904, 1906, and1908 that have authorized the user of user device 510 to access theirwellness data. In some examples, the circles next to each user's namecan be replaced with an image associated with the user. These images canbe the same image as used in device 510's contact list or can includeanother image. In the illustrated example, users 1902, 1904, 1906, and1908 have been grouped into different categories (e.g., self, family,and friends). The categories can be used to logically group userstogether or, as discussed above, can indicate a level of authorizationto view the wellness data of the other users. For example, users in the“family” category may have authorized a larger set of their wellnessdata to be viewed, while users in the “friend” category may haveauthorized a smaller set of their wellness data to be viewed. Inresponse to a selection of one of users 1902, 1904, 1906, and 1908,partitions 1910 can be updated to reflect the wellness data of theselected user. This can include updating the types of wellness datadisplayed on the partitions (e.g., based on the types of wellness datathe other user has authorized the user of user device 510 to view) aswell as the associated partial views (e.g., summary, example, or thelike) of portions the wellness data. In other examples, the list ofusers 1902, 1904, 1906, and 1908 can be displayed in response tovertically scrolling interface 900 up or down to expose the list ofusers.

FIG. 20 illustrates an exemplary process 2000 for displaying wellnessdata associated with two or more users according to various examples. Atblock 2002, a display of a first plurality of partitions associated witha first user can be displayed. The partitions can be similar oridentical to partitions 902, 904, 906, 908, 910, and 912 and can bedisplayed by a user device similar or identical to user device 510. Thepartitions can include an identifier for the type of wellness datadisplayed on the partition and a partial view (e.g., summary, example,or the like) of a portion the type of wellness data associated with thepartition. For example, an interface similar or identical to interface900 can be displayed containing various wellness data partitions 902,904, 906, 908, 910, and 912.

At block 2004, a request to view a second plurality of partitions of asecond user can be received. The second user can be a user that hasauthorized the first user to view their wellness data as describedabove. In some examples, the request can include a user input to scrollthe display of the first plurality of partitions displayed at block 2002and can be received by the user device in the form of rotation of amouse wheel, an arrow key on a keyboard, a touch and/or swipe on a touchsensitive display, or the like. Similar to the example shown in FIG. 18,the scroll direction can be in a horizontal direction relative to thecontents of the display and can be perpendicular to a scroll directionthat causes additional partitions associated with the first user to bedisplayed. However, it should be appreciated that other scrolldirections can be used. In other examples, the request to view thesecond plurality of partitions can be received in the form of aselection of the second user from a list of users. For example, thesecond user can be selected from a list of users similar to that shownin FIG. 19. The list can be displayed in response to a selection of abutton (e.g., button 901) or other selection mechanism, such asvertically scrolling the first plurality of partitions displayed atblock 2002 to expose the list of users. In response to receiving therequest to view the second plurality of partitions at block 2004, theprocess can proceed to block 2006.

At block 2006, a display of the second plurality of partitionsassociated with the second user can be displayed. In some examples, whenthe request to view the second plurality of partitions received at block2004 included a request to scroll the display of the first plurality ofpartitions, the first plurality of partitions can be translated off thedisplay in the direction of the scroll, while the second plurality ofpartitions can be translated onto the display in the same direction butfrom the opposite side of the display, as shown in FIG. 18. In otherexamples, when the request to view the second plurality of partitionsreceived at block 2004 included a selection of the second user from alist of users, the first plurality of partitions can be replaced with adisplay of the second plurality of partitions, as shown in FIG. 19.Additional requests to view wellness data partitions of other users canbe received and blocks 2004 and 2006 can be repeated to display some orall of the sets of partitions associated with users that have authorizedthe user of device 510 to view their wellness data.

It should be appreciated that the processes described above can becombined. For example, process 1700 can be combined with process 1500such that after the plurality of partitions are displayed at block 1502,a change in orientation of the user device can cause blocks 1704, 1706,and 1708 to be performed. Similarly, process 2000 can be combined withprocess 1500 such that after the plurality of partitions are displayedat block 1502, the receipt of a request to view partitions associatedwith other users can cause blocks 2004 and 2006 to be performed todisplay a plurality of partitions associated with another user.

As mentioned above, systems 500 and 600 can be configured to measure,generate, receive, or store wellness or non-wellness data continuously,intermittently, periodically, or at any other desired frequency orinterval of time. Processes 1500, 1700, and 2000 can similarly beperformed to update the display of wellness or non-wellness datacontinuously, intermittently, periodically, or at any other desiredfrequency or interval of time. For example, the device performingprocess 1500, 1700, or 2000 can receive updated wellness or non-wellnessdata from wellness database 511 or user database 516 continuously,intermittently, periodically, or at any other desired frequency orinterval of time. In some examples, the device performing process 1500,1700, or 2000 can receive updates to all wellness or non-wellness dataat the same frequency or interval of time. In other examples, the deviceperforming process 1500, 1700, or 2000 can be configured to receiveupdates to different types of data at different frequencies or intervalsof time. For example, heart rate data can be updated every second, whileweight data can be updated daily. These intervals and frequencies can bedefault values or can be selected by the user.

Dashboard View

FIG. 21 illustrates one example interface 2100 that can be displayed byuser device 510 to display a detailed view of a user's wellness ornon-wellness data. Interface 2100 can include any number of partitions2102, 2104, and 2106, each representing a different type of wellness ornon-wellness data associated with the user (e.g., data stored inwellness database 511). In some examples, the partitions can bedisplayed in a color based on the type of wellness or non-wellness datathat it represents. For example, a partition representing nutrition datacan be displayed in one color, and a partition representing of fitnessdata can be displayed in another.

In some examples, a partition can include an identification of the typeof wellness or non-wellness data that the partition represents (e.g.,calories, steps, weight, or the like), a numerical daily value of therepresented type of wellness or non-wellness data, and a graphrepresentation of the represented type of wellness or non-wellness data.For example, partition 2102 can include the text “Calories” to indicatethat it represents Calorie data, a current daily value 2110 of 1250Calories burned, and a graph representation 2108 of the Calorie dataover time throughout the day. Similarly, partition 2104 can include thetext “Steps” to indicate that it represents step data, a current dailyvalue 2111 of 3000 steps, and a graph representation 2109 of the stepdata over time throughout the day. Interface 2100 can further include apartial view of partition 2106 showing the text “Weight” to indicatethat it represents weight data, as well as a daily value 2112 of 160lbs. In the illustrated example, the graphs of each partition arenon-overlapping with each other.

In some examples, the detailed view of the user's wellness ornon-wellness data can include partitions not shown in interface 2100. Inthese examples, a user can initiate a scroll request by swiping up ordown on a touch sensitive display, by clicking and dragging on a displayusing a mouse or other input device, by manipulating a scroll-wheel, byperforming a swiping gesture on a touch pad, or the like. In response todetecting the scroll request, user device 510 can scroll the view ofinterface 2100 to display other partitions that were not previouslydisplayed (or were partially displayed, such as partition 2106).

For example, FIG. 22 illustrates an example interface 2200 that can bedisplayed in response to a user initiating a scroll request to scrollthe view of interface 2100 in an upward direction. In interface 2200,the remainder of partition 2106 can be displayed to show a graphrepresentation 2114 of the weight data over time throughout the week.Another partition 2116 can also be displayed below partition 2106 ininterface 2200. Partition 2216 can include the text “Blood Pressure” toindicate that it represents blood pressure data, a current daily value2110 of 117/67 mmHg, and a graph representation 2118 of the bloodpressure data over time throughout the week. In the example shown inFIG. 22, graph 2118 includes two vertical bars for each day. The top andbottom of the upper vertical bar for each day can represent the high andlow diastolic blood pressure values, respectively, for the day.Similarly, the top and bottom of the lower vertical bar for each day canrepresent the high and low systolic blood pressure values, respectively,for that day.

In some examples, the order of partitions within interface 2100 or 2200can be changed in response to detecting a user request to reorder thepartitions. In some examples, the request to reorder can include aselecting and holding of one of the partitions for greater than athreshold length of time. After detecting that the threshold length oftime has elapsed, user device 510 can animate the partitions in a waythat indicates that the partitions can be reordered. In some examples,the partitions can be reordered by dragging a selected partition to adesired location. However, in other examples, the partitions can bereordered in any other desired manner.

While only four partitions 2102, 2104, 2106, and 2116 are shown in thedetailed view illustrated by interfaces 2100 and 2200, it should beappreciated that the detailed view can include additional partitionsrepresenting any number and any type of wellness or non-wellness data.Similar to partitions 2102, 2104, 2106, and 2116, these additionalpartitions can include identifications of the type of wellness ornon-wellness data that the partitions represent, numerical daily valuesof the represented types of wellness or non-wellness data, and graphrepresentations of the represented types of wellness or non-wellnessdata.

In some examples, a graph view of some or all of the wellness ornon-wellness data displayed in the detailed view can be displayed inresponse to a graph-view input. In some examples, the graph-view inputcan include a detected change in orientation of user device 510. Forexample, FIG. 23 illustrates an example interface 2300 that can bedisplayed in response detecting a rotation of user device 510 to alandscape view. The graph view of interface 2300 can include data-setrepresentations 2302, 2304, 2306, and 2308, each representing adifferent set of wellness or non-wellness data. In the illustratedexample, the y-axis of the graph can represent a dependent variable ofthe various data sets, and the x-axis of the graph can represent anindependent variable. For example, if data-set representation 2302represents a set of Calorie data, then the y-axis dependent variable canbe Calories, and the x-axis independent variable can be time. Similarly,if data-set representation 2304 represents step data, then the y-axisdependent variable can be a number of steps, and the x-axis independentvariable can be time.

In some examples, the data-set representations can be displayed in acolor based on the type of wellness or non-wellness data that itrepresents. For example, a data-set representation representingnutrition data can be displayed in one color, and a data-setrepresentation of fitness data can be displayed in another. In someexamples, the colors used for the different types of wellness ornon-wellness data can correspond to the colors used to display thepartitions in the detailed views of interfaces 2100 and 2200. Forexample, a partition representing a set of nutrition data can bedisplayed in the same color as a data-set representation representingthe same set of nutrition data.

In some examples, the independent variable of the x-axis can be the samefor all data-set representations shown in the graph view. For example,the time represented by the x-axis can be the same for each data-setrepresentation.

In some examples, the dependent variable of the y-axis can be measuredin a different unit for some or all of the data-set representations. Forexample, the dependent variable for data-set representation 2302 can beexpressed in Calories, the dependent variable for data-setrepresentation 2304 can be expressed in a number of steps, the dependentvariable for data-set representation 2306 can be expressed in pounds(representing weight data), and the dependent variable for data-setrepresentation 2308 can be expressed in mmHg (representing bloodpressure data). Since these data-set representations having differentunits of measurement can be shown overlaid on the same display, adifferent vertical y-axis scaling can be used to display the variousdata-set representations. In some examples, to determine a verticalscale for one of the data-set representations, the minimum and maximumvalue of the represented data set that are to be displayed within thegraph can be determined. For example, to determine the scaling factorfor data-set representation 2302 representing Calorie data, the maximumand minimum values of the Calorie data can be determined over the spanof time represented by the x-axis of the display. In the example shownin FIG. 23, this can include determining the maximum and minimum valuesof the Calorie data over a week. The determined maximum value can bemultiplied by a first scaling factor that can have any value (e.g., avalue greater than or equal to 1, such as 1.1), and the determinedminimum value can be multiplied by a second scaling factor that can bethe same or different from the first scaling factor (e.g., a value lessthan or equal to 1, such as 0.9). The products of the maximum andminimum values multiplied by the first and second scaling factors can beassigned to the maximum vertical position (e.g., highest position on they-axis) and the minimum vertical position within the graph (e.g., lowestposition on the y-axis), respectively. This allows the data-setrepresentation to be fully displayed within the graph. For example, ifthe maximum and minimum values of the Calorie data represented bydata-set representation 2302 is 1000 Calories and 300 Calories,respectively, and if a first scaling factor of 1.1 and a second scalingfactor of 0.9 are used, then the maximum vertical position of the y-axiscan represent 1100 Calories and the minimum vertical position of they-axis can represent 270 Calories for data-set representation 2302. Thisprocess can be repeated for each of the displayed data-setrepresentations, resulting in a different scale for each of the data-setrepresentations. This advantageously allows the data-set representationsto be clearly displayed overlaid on the same graph. For example, if thesame scaling factor were instead used for all sets of data, it ispossible that the values for one data-set representation can besubstantially larger than another, causing the other data-setrepresentation to appear as a flat line.

In some examples, one or more of the displayed data-set representationscan be selected to display additional data associated with the selecteddata-set representation. In some examples, for the purpose of selectinga particular data-set representation by a user, the data-setrepresentations of the graph view shown in interface 2300 can beassociated with a range (e.g., a unique range) of vertical positionswithin the graph. For example, the graph shown in interface 2300 can bedivided into four ranges of vertical positions 2310, 2312, 2314, and2316 separated by the dashed lines. In this example, data-setrepresentation 2302 can be associated with first range of verticalpositions 2310, data-set representation 2304 can be associated withsecond range of vertical positions 2312, data-set representation 2306can be associated with third range of vertical positions 2314, anddata-set representation 2308 can be associated with fourth range ofvertical positions 2316. A selection of one of the data-setrepresentations can be made by entering a user input within a range ofvertical positions corresponding to the desired data-set representation,regardless of the horizontal position of the user input. For example, toselect data-set representation 2302, a user input in the form of a touchevent by a finger or other device on a touch sensitive display, a clickof a mouse or other device, a touch event on a touch pad, or the like,can be made at location 2318 having a vertical position located withinthe first range of vertical positions 2310. In response to detecting theuser input at location 2318 having a vertical position within firstrange 2310, user device 510 can display an indication that data-setrepresentation 2302 was selected. For example, FIG. 24 shows interface2400 that can be displayed in response to detecting the input receivedat location 2318 in interface 2300. As shown, a circle marker can bedisplayed overlaid on data-set representation 2310 at a horizontalposition corresponding to the horizontal position of location 2318.Additionally, a numerical value of 480 kcal can be displayed, indicatingthat the value of the data set represented by data-set representation2302 has a value of 480 at the horizontal position of the user input(e.g., horizontal position of location 2318). As shown, data-setrepresentation 2302 can be selected by a user input at location 2318even though the line of data-set representation 2302 is not located nearlocation 2318. This can advantageously allow a user to select a desireddata-set representation without having to select a particular portion ofthe data-set representation, which can be difficult at locations wheremultiple data-set representations overlap.

In some examples, one of the data-set representations 2302, 2304, 2306,or 2308 can represent blood pressure data. In these examples, forpurposes of generating the line of the data-set representation, thedependent variable for the blood pressure data can include an average ofthe diastolic and the systolic blood pressure. However, the numericalvalue displayed in response to a selection of the data-setrepresentation for blood pressure data can include a high value fordiastolic blood pressure, a low value for diastolic blood pressure, ahigh value for systolic blood pressure, and a low value for systolicblood pressure associated with the time corresponding to the horizontalposition of the user input.

In some examples, one of the data-set representations 2302, 2304, 2306,or 2308 can represent heart rate data. In these examples, the numericalvalue displayed in response to a selection of the data-setrepresentation for heart rate data can include a high value for heartrate and a low value for heart rate associated with the timecorresponding to the horizontal position of the user input.

In some examples, the indication of a selection displayed in response todetecting a user input can further include highlighting an area belowthe line of the selected data-set representation. For example, the areabelow the line of the selected data-set representation can be darkened,brightened, displayed with a different color, or otherwise highlightedrelative to other portions of the graph to change the line graph into anarea graph of the selected data set. In some examples, the data-setrepresentations that are not currently selected can be removed from thedisplay, greyed out, or otherwise made less visible within the graph.

In some examples, a user input can be continuously applied to thedisplayed graph and moved in a horizontal direction within one of therange of vertical positions to scrub through values of the selecteddata-set representation. For example, in response to detecting that theuser input received at location 2318 is moved in the left direction, thecircle marker displayed over data-set representation 2302 can beanimated such that it appears to move along the line of data-setrepresentation 2302 at horizontal positions corresponding to the currenthorizontal position of the user input. Similarly, the displayed valuecan change to reflect the value of the data set represented by data-setrepresentation 2302 at the horizontal position of the user input.

In some examples, the vertical ranges of values within the graphassociated with the data-set representations can be static. In otherexamples, the vertical ranges of values within the graph associated withthe data-set representations can change. For example, in response todetecting a user input at a location within first range 2310, the sizeof first range 2310 can expand based on a length of time that thedetected user input remains within first range 2310. As a result, theother vertical ranges can contract, or decrease in size. In someexamples, the size of first range 2310 can expand to cover the entiregraph. In other examples, the size of first range 2310 can expand to apredefined limit. Expanding the size of a selected range of verticalpositions advantageously provides the user with a greater tolerance forvertical deviation as the user moves their user input in a horizontaldirection to select different portions of a data-set representation.

In some examples, interface 2300 or 2400 can include a compare option2320 to select the sets of wellness or non-wellness data that are to bedisplayed within the graph view. For example, FIG. 25 illustrates anexample interface 2500 that can be displayed in response to a userselection of compare option 2320 in interface 2300 or 2400. As shown,interface 2500 includes a list of types of wellness or non-wellness datathat can be displayed within the graph view. Each type of wellness ornon-wellness data can be associated with a selectable option, such asoption 2502, to allow the user to add or remove the associated type ofwellness or non-wellness data from the graph view. In the illustratedexample, the data sets corresponding to Calorie data, step data, bloodpressure data, and heart rate data are selected to be displayed withinthe graph view, while weight data is not. In some examples, the list ofwellness or non-wellness data displayed within interface 2500 caninclude the types of wellness or non-wellness represented by thepartitions of interfaces 2100 and 2200.

In some examples, the detailed view of the wellness or non-wellness datacan be displayed in response to a detailed-view input received while anyof interfaces 2300, 2400, or 2500 are being displayed. In some examples,the detailed-view input can include a detected change in orientation ofuser device 510. For example, interface 2100 or 2200 can be displayed inresponse to detecting a rotation of user device 510 to a portrait view.

While the graph view shown in interfaces 2300 and 2400 include fourdata-set representations, it should be appreciated that the graph caninclude any number of data-set representations. Additionally, the numberof ranges of vertical positions can change based on the number ofdisplayed data-set representations (e.g., to be equal to the number ofdisplayed data-set representations). For example, if six data-setrepresentations are displayed within the graph, then six discrete rangesof vertical positions can be associated with the data-setrepresentations to allow a user to select the desired data-setrepresentation.

FIG. 26 illustrates an example process 2600 for displaying wellness ornon-wellness data according to various examples. Process 2600 can beperformed at an electronic device (e.g., device 510) with a display. Insome examples, the display can include a touch-sensitive display. Inother examples, the display can be separate from a touch-sensitivesurface. Some blocks of process 2600 can be combined and/or the order ofsome blocks can be changed.

As described below, process 2600 provides an intuitive way to selectoverlapping data-set representations in a graph view. The process allowsa user to select a particular data-set representation without having totarget a specific location on the data-set representation, which can bedifficult at locations where multiple data-set representations overlap.

At block 2602, a graph view of wellness or non-wellness data can bedisplayed on a display of a user device (e.g., user device 510). Forexample, an interface similar or identical to interface 2300 or 2400 canbe displayed. The graph view can include a first data-set representation(e.g., data set representation 2302) of a first data set in which afirst dependent variable varies as an independent variable changes and asecond data-set representation (e.g., data set representation 2304) of asecond data set in which a second dependent variable varies as theindependent variable changes. The first data-set representation can beassociated with a first range of vertical positions within the graph(e.g., first range 2310) and the second data-set representation can beassociated with a second range of vertical positions within the graph(e.g., first range 2312).

In some examples, the first data-set representation can be displayed inthe graph overlapping the second data-set representation. For example,data-set representations 2302, 2304, 2306, and 2308 are shown asoverlapping in interfaces 2300 and 2400. In some examples, the firstdata-set representation and the second data-set representation can becolored-coded based on a type of data that they represent.

In some examples, the first data set can include a first set of wellnessdata, and the second data set can include a second set of wellness data.In some examples, the dependent variable for the first data set can bemeasured in different units from the dependent variable for the seconddata set.

In some examples, the first range of vertical positions can be uniquelyassociated with the first data-set representation, and the second rangeof vertical positions can be uniquely associated with the seconddata-set representation. For example, first range 2310 is uniquelyassociated with data-set representation 2302 and second range 2312 isuniquely associated with data-set representation 2304 in interfaces 2300and 2400.

In some examples, a vertical scale for displaying the first data-setrepresentation can be different from a vertical scale for displaying thesecond data-set representation. In these examples, displaying the graphcan include determining a vertical scale for the first data-setrepresentation based on the maximum and minimum values of the firstdependent variable of the first data-set representation that are to bedisplayed in the graph. Displaying the graph can further includedetermining a vertical scale for the second data-set representationbased on the maximum and minimum values of the second dependent variableof the second data-set representation that are to be displayed in thegraph. In some examples, the vertical scale for the first data-setrepresentation can be defined by a maximum vertical position within thegraph corresponding to a first multiplying factor multiplied by themaximum value of the first dependent variable of the first data-setrepresentation that are to be displayed in the graph, and a minimumvertical position within the graph corresponding to a second multiplyingfactor multiplied by the minimum value of the first dependent variableof the first data-set representation that are to be displayed in thegraph. In some examples, the vertical scale for the second data-setrepresentation can be defined by a maximum vertical position within thegraph corresponding to a third multiplying factor multiplied by themaximum value of the second dependent variable of the second data-setrepresentation that are to be displayed in the graph, and a minimumvertical position within the graph corresponding to a fourth multiplyingfactor multiplied by the minimum value of the second dependent variableof the second data-set representation that are to be displayed in thegraph.

At block 2604, a user input can be detected at a location on thedisplay. Detecting the user input can include detecting a touch or hoverevent by a finger or other device on a touch sensitive display, a clickof a mouse or other device, a touch or hover event on a touch pad, orthe like.

At block 2606, a location of the user input can be determined. Forexample, the vertical and horizontal positions (e.g., y and x-axiscoordinates) of the user input can be determined. In response todetermining that the location of the user input on the display detectedat block 2604 has a vertical position associated with the first range ofvertical positions, an indication of a selection of the first data-setrepresentation can be displayed. Alternatively, in response todetermining that the location of the user input on the display detectedat block 2604 has a vertical position associated with the second rangeof vertical positions, an indication of a selection of the seconddata-set representation can be displayed.

In some examples, displaying the indication of a selection can includedisplaying a marker overlaid on the selected data-set representation ata horizontal position corresponding to the horizontal position of thelocation of the user input. For example, a circle marker can bedisplayed over data-set representation 2302 in interface 2400 of FIG. 24in response to detecting a user input at location 2318 in interface2300. In some examples, displaying the indication of a selection canfurther include displaying a numerical value of a data entry of the dataset represented by the selected data-set representation. The data entrycan be associated with a value of the independent variable correspondingto the horizontal position of the location of the detected user input.For example, a numerical value of 480 kcal can be displayed in responseto receiving a user input at location 2318.

In some examples, the first data set or the second data set can includeblood pressure data. In these examples, the displayed numerical value ofthe data entry can include a high value for diastolic blood pressure, alow value for diastolic blood pressure, a high value for systolic bloodpressure, and a low value for systolic blood pressure. In some examples,the dependent variable of the first data-set representation or thesecond data-set representation can include average of blood pressurevalues.

In other examples, the first data set or the second data set can includeheart rate data. In these examples, the displayed numerical value of thedata entry can include a high value for heart rate and a low value forheart rate.

In some examples, the first data-set representation can include a firstline in the graph. In these examples, displaying the indication that thefirst data-set representation has been selected can include highlightingan area below the first line. For example, the area below the line ofthe selected data-set representation can be darkened, brightened,displayed with a different color, or otherwise highlighted relative toother portions of the graph to change the line graph into an area graphof the selected data set. In some examples, the data-set representationsthat are not currently selected can be removed from the display, greyedout, or otherwise made less visible within the graph.

In some examples, the first range of vertical positions within the graphcan expand based on a length of time that the user input is detectedwhile a vertical position of the location of the user input is withinthe first range of vertical positions. In other examples, the secondrange of vertical positions within the graph can expand based on alength of time that the user input is detected while the verticalposition of the location of the user input is within the second range ofvertical positions.

At block 2608, a detailed-view input can be detected at the electronicdevice. In some examples, detecting the detailed-view input can includedetecting a change in orientation of the electronic device whiledisplaying the graph. For example, detecting the detailed-view input caninclude detecting a change in orientation of the electronic device froma landscape view (e.g., shown in FIGS. 23-25) to a portrait view (e.g.,shown in FIGS. 21-22). In other examples, the detailed-view input caninclude other types of inputs.

At block 2610, in response to detecting the detailed-view input, adetailed view of the first data set and the second data set can bedisplayed. For example, a detailed view similar or identical to thoseshown in interfaces 2100 and 2200 can be displayed. The detailed viewcan include a first partition associated with the first data set (e.g.,partition 2102) and a second partition associated with the second dataset (e.g., partition 2104).

In some examples, the first partition can include a first graphrepresentation of the first data set (e.g., graph 2108), and the secondpartition can include a second graph representation of the second dataset (e.g., graph 2110). In some examples, unlike the first and seconddata-set representation of the graph view, the first graphrepresentation can be non-overlapping with the second graphrepresentation in the detailed view.

In some examples, the first partition can be displayed in a colormatching a color of the first data-set representation, and the secondpartition can be displayed in a color matching a color of the seconddata-set representation. For example, partition 2102 can be displayed ina color matching a color of data-set representation 2302, and partition2104 can be displayed in a color matching a color of data-setrepresentation 2304.

In some examples, process 2600 can further include detecting a requestto scroll the detailed view and, in response to detecting the request toscroll the detailed view, scrolling the detailed view. For example, thedetailed view shown in interface 2100 can be scrolled in the upwarddirection to display interface 2200 containing other partitions thatwere not previously displayed.

In some examples, process 2600 can further include detecting a requestto reorder the first partition and the second partition and, in responseto detecting the request to reorder the first partition and the secondpartition, reordering the first partition and the second partitionwithin the detailed view. In some examples, detecting the request toreorder can include detecting a selection of one of the partitions forgreater than a threshold length of time. After detecting the selectionfor the threshold length of time, user device 510 can animate thepartitions in a way that indicates that the partitions can be reordered.The partitions can be displayed reordered in response to detecting thata selected partition is dragged to a new location within the detailedview.

In some examples, process 2600 can further include detecting agraph-view input at the electronic device and, in response to detectingthe graph-view input, displaying the graph comprising the first data-setrepresentation of the first data set and the second data-setrepresentation of the second data set. In some examples, detecting thegraph-view input can include detecting a change in orientation of theelectronic device. For example, interface 2300 can be displayed inresponse to detecting a change in orientation of the electronic devicefrom a portrait view to a landscape view.

It should be understood that the particular order in which theoperations in FIG. 26 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other processes described herein (e.g.,processes 800, 1500, 1700, 2000, 2600, 3700, or 4400) are alsoapplicable in an analogous manner to process 2600 described above withrespect to FIG. 26. For brevity, these details are not repeated here.

Input and Output of Heath Data with Granularity

FIG. 27 illustrates one example interface 2700 that can be displayed byuser device 510 to display a user's wellness or non-wellness data.Interface 2700 can include a list 2702 of categories of wellness ornon-wellness data. The categories can include one or more sub-categoriesof wellness or non-wellness data. The sub-categories can further includeany number of additional sub-categories. For example, the category“Fitness” can include sub-categories “Body Mass Index,” “Body FatPercentage,” “Height,” “Body Mass,” “Lean Body Mass,” “Steps,”“Distance,” “Calories Burned,” “Active Hours,” and “Flights of Stairs.”The category “Vital Signs” can include sub-categories “Heart Rate,”“Systolic Blood Pressure,” “Diastolic Blood Pressure,” “OxygenSaturation,” “Respiratory Rate,” and “Body Temperature.” The category“Lab Results” can include sub-categories “Blood Glucose” and “BloodAlcohol Content.” The category “Nutrition” can include sub-categories“Total Fat,” “Polyunsaturated Fat,” “Monounsaturated Fat,” “SaturatedFat,” “Cholesterol,” “Sodium,” “Potassium,” “Carbohydrates from Sugar,”“Dietary Fiber,” “Sugars,” “Dietary Calories,” “Calories from Fat,”“Protein,” “Vitamin A,” “Vitamin B6,” “Vitamin B12,” “Vitamin C,”“Vitamin D,” “Vitamin E,” “Vitamin K,” “Calcium,” “Iron,” “Thiamin,”“Riboflavin,” “Niacin,” “Folic Acid,” “Biotin,” “Pantothenic Acid,”“Phosphorus,” “Iodine,” “Magnesium,” “Zinc,” “Selenium,” “Copper,”“Manganese,” “Chromium,” “Molybdenum,” and “Chloride.” The category“Diagnostics” can include sub-categories “Number of Time Fallen,”“Galvanic Skin Response,” and “Body Heat Flux.” The category“Medications” can include sub-category “Inhaler Use.” The category“Sleep” can include subcategories “Hours Slept.” The category “Me” caninclude sub-categories “Name,” “Birthdate,” “Gender,” “Blood Type.” Itshould be appreciated that the lists above are provided only asexamples, and that additional or fewer categories can be included withininterface 2700. Additionally, it should be appreciated that thecategories of interface 2700 can include additional or fewersub-categories.

In some examples, each item in list 2702 can include an indicator 2704that can be color-coded based on the type of wellness or non-wellnessdata of the associated item in list 2702. For example, the indicator2704 associated with “Fitness” can have a different color than theindicator 2704 associated with “Vital Signs.” In some examples, theitems in list 2702 can further include a selectable option 2706 that canbe used to expand the associated category.

For example, FIG. 28 illustrates interface 2800 that can be displayed inresponse to a selection of option 2706 associated with “Fitness.” Asshown, interface 2800 can include a list 2802 of sub-categories thatfall under the broader category of “Fitness” that was selected ininterface 2700. The list 2802 of sub-categories can be displayed inplace of the previously displayed list 2702. Similar to list 2702, theitems in list 2802 can include an indicator 2804 that can be color-coredbased on the type of wellness or non-wellness data of the associateditem in list 2802. In this example, since all of the sub-categoriesdisplayed within list 2802 fall under the same category or type ofwellness or non-wellness data, the indicators 2804 associated with eachitem can be the same color. In some examples, the color of indicators2804 associated with the items in list 2802 can be the same color asindicator 2704 associated with “Fitness.” In other examples, the colorof indicators 2804 associated with the items in list 2802 can be adifferent shade of the color of indicator 2704 associated with“Fitness.” For example, indicators 2804 can be light green, whileindicator 2704 associated with “Fitness” can be dark green.

Referring back to FIG. 27, interface 2700 (and interface 2800) canfurther include search box 2708 for performing keyword searches withinthe categories listed in list 2702. For example, FIG. 29 illustratesinterface 2900 that can be displayed in response to a user entering thesearch query “Calories” in search box 2708. As shown, interface 2900 caninclude a list 2902 of sub-categories that match the search query“Calories.” The sub-categories can be sub-categories of any of thecategories of list 2702. For “Calories Burned” can be a sub-category of“Fitness,” “Dietary Calories” can be a sub-category of “Nutrition,” and“Calories From Fat” can be a sub-category of “Nutrition.” Interface 2900can further include indicators 2904 associated with the items in list2902. Similar to indicators 2704 and 2804, indicators 2904 can becolor-coded based on the type of wellness or non-wellness data of theassociated item in list 2902. In this example, indicator 2904 of“Dietary Calories” can be the same color as indicator 2904 of “CaloriesFrom Fat” since they both fall within the broader category of“Nutrition.” In some examples, the color of indicators 2904 of “DietaryCalories” and “Calories From Fat” can be the same color as indicator2704 for “Nutrition.” In other examples, the color of indicators 2904 of“Dietary Calories” and “Calories From Fat” can be a different shade ofthe color of indicator 2704 for “Nutrition.” The indicator 2904 for“Calories Burned” can be a different color from indicators 2904 of“Dietary Calories” and “Calories From Fat” since “Calories Burned” fallswithin a different category (e.g., “Fitness”). In some examples, thecolor of indicator 2904 of “Calories Burned” can be the same color asindicator 2704 for “Fitness.” In other examples, the color of indicator2904 of “Calories Burned” can be a different shade of the color ofindicator 2704 for “Fitness.”

In some examples, any of the sub-categories shown in interfaces 2800 and2900 can be selected to display a detailed view of the sub-category. Forexample, FIG. 30 illustrates an example interface 3000 that can bedisplayed in response to a selection of “Calories Burned” from eitherinterface 2800 or 2900. As shown, interface 3000 can include a textindication of the type of wellness or non-wellness data being displayedin the detailed view. For example, interface 3000 include the text“Calories Burned” to indicate that the information displayed withininterface 3000 represents information associated with Calories burned.

In some examples, interface 3000 can further include a current dailyvalue 3004 of 1250 kcal and a graph representation 3002 showing thenumber of Calories burned over time throughout the day. Interface 3000can further include “Show All Data” option 3006 that can be used todisplay all data that falls within the sub-category of “CaloriesBurned.” For example, FIG. 32 illustrates an example interface 3200 thatcan be displayed in response to a selection of option 3006 in interface3000. As shown, interface 3200 can include a list 3202 of all dataentries that represent calories burned (e.g., stored in wellnessdatabase 511). As shown, the data entries in list 3202 can include anumerical value of the data entry and an associated date (and can alsoinclude a time) that the corresponding data entry was recorded. Forexample, the first data entry in list 3202 can include the number 860associated with date Mar. 1, 2014, indicating that 860 Calories wereburned on Mar. 1, 2014. The data entries in list 3202 can furtherinclude an indicator 3204. Indicator 3204 can include a graphic, text,or other image that represents the source of the data entry. Forexample, if the first data entry was obtained from a wearable electronicDevice 1, indicator 3204 associated with that data entry can include animage of the logo of the company that manufactured Device 1 or someother image associated with Device 1. Similarly, if the second dataentry in list 3202 was obtained from a software application App 1,indicator 3204 associated with the second data entry can include animage associated with a logo of the company that created App 1 or someother image associated with App 1.

While shown for Calories burned, it should be appreciated that a list ofdata entries associated with any type of sub-category of wellness ornon-wellness data can be displayed in a similar manner.

Referring back to FIG. 30, interface 3000 can further include “Add DataPoint” option 3008 that can be used to display an interface for manuallyentering a data entry within the sub-category of “Calories Burned.” Forexample, FIG. 33 illustrates an example interface 3300 that can bedisplayed in response to a selection of option 3008 in interface 3000.As shown, interface 3300 can include fields 3302, 3304, and 3306 forentering the date, time, and number of Calories burned, respectively,for the data entry being input. Interface 3300 can further includenumerical input pad 3308 for populating fields 3302, 3304, and 3306.Interface 3300 can further include “Add” button 3310 that can beselected to add the information contained in interface 3300 as a dataentry within the Calories burned sub-category (e.g., to be stored inwellness database 511). Interface 3300 can further include “Cancel”button 3312 for canceling entry of the data entry.

Referring back to FIG. 30, interface 3000 (and interface 3100) canfurther include “Show On Dashboard” option 3012 having option 3020 forselectively causing the associated sub-category of data (e.g., CaloriesBurned) to be displayed in the detailed view of interfaces 2100 and2200. When the switch of option 3020 is placed in the on position, theassociated sub-category of data can be included within the detailed viewof interfaces 2100 and 2200. However, when the switch of option 3020 isplaced in the off position, the associated sub-category of data may notbe included within the detailed view of interfaces 2100 and 2200.

As shown in FIG. 30, interface 3000 can further include graphic 3014.Graphic 3014 can include any image or other graphical representation ofthe wellness or non-wellness data represented displayed in interface3000. For example, graphic 3014 can include a balance showing therelative values of Calories consumed and Calories expended by the user.However, it should be appreciated that any other graphic or image can beshown.

In some examples, the detailed view of the sub-category can furtherinclude additional information not shown in interface 3000. In theseexamples, a user can initiate a scroll request by swiping up or down ona touch sensitive display, by clicking and dragging on a display using amouse or other input device, by manipulating a scroll-wheel, byperforming a swiping gesture on a touch pad, or the like. In response todetecting the scroll request, user device 510 can scroll the view ofinterface 3000 to display information that was not previously displayed(or was partially displayed).

For example, FIG. 31 illustrates an example interface 3100 that can bedisplayed in response to a user initiating a scroll request to scrollthe view of interface 3000 in an upward direction. In interface 3100,graphic 3014 and options 3006, 3008, 3010, and 3012 can still bedisplayed, but can be located closer to the top of the display.Interface 3100 can further include text description 3022 below graphic3014. Text description 3022 can include a text describing what thewellness or non-wellness data shown in interface 3100 represents. Forexample, text description 3022 can provide an explanation about what“Calories Burned” represents, such as how it is calculated, what anaverage daily value is for a typical person, how to increase the amountof Calories burned, or the like.

Referring back to FIG. 30, interface 3000 can further include “ShareData” option 3010 having option 3016 for turning data sharing on or off.Data sharing can represent the ability for other devices or applicationsto access a user's wellness or non-wellness data (e.g., stored inwellness database 511). For example, FIG. 34 illustrates an exampleinterface 3400 that can be displayed in response to a selection ofoption 3010 in interface 3000. As shown, interface 3400 can includeshare option 3402 having selectable option 3412. The position of theswitch of option 3412 can be used to turn data sharing on or off. Forexample, when moved to the right, as shown in FIG. 34, the switch ofoption 3412 can turn on sharing option 3402. However, when moved to theleft, the switch of option 3412 can turn off sharing option 3402.

Interface 3400 can further include a list 3404 of known possibledestinations of wellness or non-wellness data. This list can includeknown devices or software applications that can potentially receive auser's wellness or non-wellness data (e.g., stored in wellness database511). When option 3412 of share option 3402 is moved to the offposition, data sharing for all listed devices and applications can beturned off. As such, selectable options 3414, 3416, and 3418 can beremoved from interface 3400 or otherwise made inactive. When option 3412of share option 3402 is moved to the on position, selectable options3414, 3416, and 3418 associated with the destinations in list 3404 canbe displayed or made selectable. Similar to option 3412, the position ofthe switches of options 3414, 3416, and 3418 can be changed to turn datasharing on or off for the associated destination. For example, option3414 for Device 1 is in the off position, indicating that data sharingis not turned on for Device 1. Options 3416 and 3418, however, are inthe on position, indicating that data sharing is turned on for App 1 andApp 2. When data sharing is turned on, the associated device orapplication can access the user's wellness or non-wellness data (e.g.,stored in wellness database 511). For example, App 1, which canrepresent a weight tracking application, can access a user's fitness andnutrition data to track the user's caloric intake and outtake. When datasharing is turned off, the associated device or application may beprevented from accessing the user's wellness or non-wellness data (e.g.,stored in wellness database 511). For example, Device 1 may be unable toaccess data stored in wellness database 511.

Interface 3400 can further include source list 3406 containing a list ofknown devices and applications that can potentially provide wellness ornon-wellness data (e.g., to be stored in wellness database 511). Thedevices and applications in source list 3406 can be arranged in an orderbased on their priority. For example, as shown, Device 1 has priorityover Device 2, which has priority over App 3. These relative prioritiescan be used to de-duplicate wellness or non-wellness data generated bytwo or more of the sources. For example, if Device 1 represents afitness-tracking watch, and Device 2 represents a mobile phone, it ispossible that both devices can provide step data associated with theuser. Thus, by prioritizing the different sources, data from a higherranked source can be used in place of data from a lower ranked source,or otherwise prioritized over data from the lower ranked source. Thiscan be advantageous when one device is more likely to produce moreaccurate results than another. In some examples, duplicate data entriescan be detected by identifying two or more data entries having metadataindicating that they are of the same type (e.g., step data, Caloriesburned, etc.) and having an associated timestamp that is within athreshold length of time from each other.

In some examples, interface 3400 can further include edit option 3408for changing the order of the sources of source list 3406. For example,in response to a selection of option 3408, each item in source list 3406can be moved (e.g., by clicking and dragging, etc.) relative to eachother. The new order of sources within source list 3406 can define a newprioritization between sources.

In some examples, the “Sources” option of source list 3406 can beselected to display a more detailed view of the sources. For example,FIG. 35 illustrates an example interface 3500 that can be displayed inresponse to a selection of the “Sources” option of source list 3406. Asshown, interface 3500 can include a source list 3506 similar to sourcelist 3406. However, source list 3506 can further include sources App 2and App 1, which were not displayed within interface 3400 because theywere unable to be fit within the display. Interface 3500 can furtherinclude a numerical indicator associated with a source (e.g., Device 1)that indicates a number of new types of wellness or non-wellness datathat the associated source can provide. For example, since the last timethe user viewed interface 3500, Device 1 is now able to provide two newtypes of data (e.g., Calories burned and flights of stairs climbed).Interface 3500 can further include option 3510 associated with thesources in source list 3506 to provide more detailed control over thetypes of data that each source can provide.

For example, FIG. 36 illustrates an example interface 3600 that can bedisplayed in response to a selection of option 3510 in interface 3500 oroption 3410 in interface 3400 associated with Device 1. As shown,interface 3600 can include upload option 3602 having selectable option3604. The position of the switch of option 3604 can be used to turn datauploading from the device or application on or off (e.g., to be storedin wellness data base 511). For example, when moved to the right, asshown in FIG. 36, the switch of option 3604 can turn on data uploadingby Device 1. However, when moved to the left, the switch of option 3604can turn off data uploading by Device 1.

Interface 3600 can further include a list 3606 of data types that can beprovided by Device 1. When option 3412 of share option 3604 is moved inthe off position, data uploading for all listed types of data can beturned off. As such, selectable options 3608, 3610, 3612, and 3614 canbe removed from interface 3600 or otherwise made inactive. When option3604 of upload data option 3602 is moved to the on position, selectableoptions 3608, 3610, 3612, and 3614 associated with the list 3606 of datatypes can be displayed or made selectable. Similar to option 3604, theposition of the switches of options 3608, 3610, 3612, and 3614 can bechanged to turn data uploading on or off for the associated types ofdata. For example, option 3608 for Blood Pressure is in the offposition, indicating that data uploading is not turned on for BloodPressure data from Device 1. Options 3610, 3612, and 3614, however, arein the on position, indicating that data uploading is turned on forCalorie, Step, and Stairs Climbed data. When data uploading is turnedon, the associated type of data can be provided by the device orapplication to be stored by user device 510 (e.g., in wellness database511). For example, Calorie data generated by Device 1 can be received byuser device 510 from Device 1 and stored in wellness database 511. Whendata uploading is turned off, the associated type of data may not beprovided by the device or application to be stored by user device 510(e.g., in wellness database 511). For example, blood pressure datagenerated by Device 1 may not be received by user device 510 from Device1 and stored in wellness database 511. The options of interface 3600advantageously allow a user to specifically define what types of datacan be provided by a particular device or application.

While the examples shown in FIGS. 30-34 were for Calories burned, itshould be appreciated that similar interfaces can also be displayed forother types of wellness or non-wellness data.

FIG. 37A illustrates an example process 3700 for managing and displayingwellness or non-wellness data according to various examples. Process3700 can be performed at an electronic device (e.g., device 510) with adisplay. In some examples, the display can include a touch-sensitivedisplay. In other examples, the display can be separate from atouch-sensitive surface. Some blocks of process 3700 can be combinedand/or the order of some blocks can be changed.

As described below, process 3700 provides an intuitive way to managesources and destinations of data stored in wellness database 511. Theprocess allows a user to specify which devices and applications canaccess data in wellness database 511, as well as to specify the devicesand applications that can serve as sources for data to be stored inwellness database 511. Additionally, for the sources, the user canspecify what types of data those sources can provide and which sourcestake priority over others. This can be advantageous when one device ismore likely to produce more accurate results than another.

At block 3702, information identifying a plurality of approved sourcesof wellness data can be received by a user device (e.g., user device510) from a user. In some examples, the information identifying theplurality of approved sources can identify one or more types of wellnessor non-wellness data that are approved to be received from the pluralityof approved sources and stored in a wellness database (e.g., wellnessdatabase 511). For example, the information identifying the plurality ofapproved sources can be received via an interface similar or identicalto interfaces 3400, 3500, and 3600. In these examples, a user canspecify which types of data can be provided by each of the plurality ofapproved sources to be stored in the wellness database.

At block 3704, information identifying a plurality of approveddestinations of wellness or non-wellness data can be received by a userdevice (e.g., user device 510) from the user. For example, theinformation identifying the plurality of approved destinations can bereceived via an interface similar or identical to interface 3400. Inthese examples, a user can specify which destinations are approved toaccess data from the wellness database.

In some examples, the plurality of approved sources can include anelectronic device or a software application. For example, an approvedelectronic device, such as a watch, a mobile phone, or the like, canprovide wellness or non-wellness data to user device 510 to be stored inwellness database 511. Similarly, an approved software application on orotherwise associated with user device 510 can provide wellness ornon-wellness data to user device 510 to be stored in wellness database511. In some examples, the approved software application can be asoftware application associated with an electronic device and is capableof communicating with the electronic device.

Similarly, in some examples, the plurality of approved destinations caninclude an electronic device or a software application. For example, anapproved electronic device, such as a watch, a mobile phone, or thelike, can access wellness or non-wellness data stored in wellnessdatabase 511. Similarly, an approved software application on orotherwise associated with user device 510 can access wellness ornon-wellness data stored in wellness database 511. In some examples, theapproved software application can be a software application associatedwith an electronic device and is capable of communicating with theelectronic device.

In some examples, the plurality of approved sources can be rankedamongst each other. In some examples, an interface similar or identicalto interface 3400 can be used to display and adjust the relative rankingof the approved sources. For example, as shown in interface 3400, Device1 can be ranked higher than Device 2 to prioritize data from Device 1over data from Device 2, and Device 2 can be ranked higher than App 3 toprioritize data from Device 1 and Device 2 over data from App 3.

In some examples, process 3700 can further include, at block 3706,identifying a first wellness data entry and a second wellness data entrythat are duplicates of one another. In some examples, this can includeidentifying a first wellness data entry in the wellness database thatwas received from a first approved source of the plurality of approvedsources, the first wellness data entry comprising a first wellness datatype and a first timestamp, and identifying a second wellness data entryin the wellness database that was received from a second approved sourceof the plurality of approved sources, the second wellness data entrycomprising a second wellness data type and a second timestamp, whereinthe first wellness data type and the second wellness data type are thesame, and wherein the first timestamp is within a threshold length oftime from the second timestamp. For example, a first data entry can havea type of “step data” and an associated timestamp of 2:30 p.m. on Mar.1, 2014. The second data entry can have a type of “step data” and anassociated timestamp of 2:31 p.m. on Mar. 1, 2014. If the thresholdlength of time used at block 3706 is 5 minutes, it can be determinedthat the first data entry and the second data entry are of the same datatype and include timestamps that are within a threshold length of timefrom each other. This can indicate that the first data entry and thesecond data entry are likely duplicate entries representing the sameactions performed by the user.

At block 3708, one of the first data entry and the second data entry canbe prioritized or otherwise identified as being preferred over the otherbased on a ranking of the plurality of sources. For example, asdiscussed above, the plurality of approved sources can be ranked amongsteach other (e.g., as shown in interface 3400). In some examples, if thefirst approved source providing the first data entry is identified bythe user as being preferred over the second approved source, block 3708can include using the first wellness data entry instead of using thesecond wellness data entry. For example, this can include deleting thesecond data entry from wellness database 511 or otherwise ignoring thesecond data entry for purposes of being displayed or presented to theuser. In other examples, if the first approved source has beenidentified by the user as being preferred over the second approvedsource, then block 3706 can include prioritizing the first wellness dataentry over the second wellness data entry. A data entry that isprioritized over another can be used in place of the other (e.g.,displayed, used in calculations, or the like in favor of the other dataentry).

In other examples, if the second approved source has been identified bythe user as being preferred over the first approved source, then block3706 can include prioritizing the second wellness data entry over thefirst wellness data entry. A data entry that is prioritized over anothercan be used in place of the other (e.g., displayed, used incalculations, or the like in favor of the other data entry).

In some examples, as shown in FIG. 37B, process 3700 can furtherinclude, at block 3710, displaying, by the electronic device on thedisplay, a plurality of categories of wellness data stored in thewellness database. For example, an interface similar or identical tointerface 2700 can be displayed. The interface can include any amount orany type of categories of wellness or non-wellness data.

At block 3712, a selection of a category of wellness data from thedisplayed plurality of categories of wellness data can be detected atthe electronic device. For example, a selection of one of the categoriesdisplayed in an interface similar or identical to interface 2700 madevia a touch event by a finger or other device on a touch sensitivedisplay, a click of a mouse or other device, a touch event on a touchpad, or the like, can be detected. In some examples, each of thedisplayed plurality of categories can include an indicator (e.g.,indicator 2704) that can be color-coded based on the type of wellness ornon-wellness data of the category. For example, the indicator associatedwith “Fitness” can have a different color than the indicator associatedwith “Vital Signs.”

At block 3714, one or more sub-categories of the category of wellnessdata can be displayed in response to detecting the selection of thecategory of wellness data. For example, an interface similar oridentical to interface 2800 containing a list of sub-categories fallingwithin the category selected at block 3712 can be displayed. In someexamples, the displayed interface can include indicators that can becolor-cored based on the type of wellness or non-wellness data that itrepresents.

At block 3716 a selection of a sub-category from the displayed one ormore sub-categories can be detected. For example, a selection of one ofthe sub-categories displayed in an interface similar or identical tointerface 2800 made via a touch event by a finger or other device on atouch sensitive display, a click of a mouse or other device, a touchevent on a touch pad, or the like, can be detected.

At block 3718, a detailed view of the selected sub-category can bedisplayed in response to detecting the selection of the sub-category atblock 3716. For example, an interface similar or identical to interface3100 can be displayed. The detailed view of the sub-category can includea graphical representation of the sub-category of data (e.g., graph3002) and a numerical daily value (e.g., daily value 3004). The detailedview can further include options to show all data (e.g., option 3006),add a data point (e.g., option 3008), share data (e.g., option 3010),and show on dashboard (e.g., option 3012). The detailed view can furtherinclude a graphic representation of the sub-category (e.g., graphic3014) and a text description of the sub-category (e.g., description3022),

In some examples, process 3700 can include displaying an interfacesimilar or identical to interface 3300 in response to a selection of theadd a data point option (e.g., option 3008). The interface can includeone or more input fields (e.g., fields 3302, 3304, and 3306) forentering information associated with the wellness data entry. In someexamples, process 3700 can further include receiving a wellness dataentry to be stored in the wellness database that was input into theinput field (e.g., input into fields 3302, 3304, and 3306).

In some examples, process 3700 can further include displaying aninterface similar or identical to interface 3200 in response to aselection of the show all data option (e.g., option 3006). The interfacecan include a plurality of wellness data entries corresponding to thesub-category stored in the wellness database (e.g., entries in list3202) In some examples, each of the plurality of wellness data entriescan include a numerical value of the data entry, a timestamp, and anidentification of a source of the data entry (e.g., indicator 3204).

In some examples, process 3700 can further include displaying a datasharing interface similar or identical to interface 3400 in response toa selection of the share data option (e.g., option 3010). The interfacecan include the plurality of approved sources (e.g., source list 3406)and the plurality of approved destinations (e.g., list 3404). In someexamples, a request to reorder the displayed plurality of approvedsources can be detected by the electronic device. For example, aselection of edit button 3408 can be received and movement of one ormore of the sources in source list 3406 can be detected. In response todetecting the request to reorder the displayed plurality of approvedsources, the displayed plurality of approved sources can be reordered inaccordance with the detected request to reorder the displayed pluralityof approved sources

In some examples, the data sharing interface (e.g., interface 3400) canfurther include options to add an approved destination to the pluralityof approved destinations and to remove an approved destination from theplurality of approved destinations (e.g., options 3412, 3414, 3416, and3418).

In some examples, process 3700 can further include receiving, at theelectronic device, a search query. In response, one or moresub-categories of the plurality of categories that match the searchquery can be displayed. The displayed one or more sub-categories thatmatch the search query can be color-coded based on their respectivecategories. For example, a search query can be received from a searchbox (e.g., search box 2708) displayed within an interface similar oridentical to interface 2700 or 2800. A search results interface similaror identical to interface 2900 can be displayed in response to thesearch query. The search results interface can include the one or moresub-categories that match the search query.

In some examples, process 3700 can further include displaying, on thedisplay, a source interface comprising a list of known sources. Forexample, an interface similar or identical to interface 3500 can bedisplayed having a list of known sources (e.g., list 3506). The sourceinterface can further include a numerical indicator associated a knownsource of the known sources that represents a number of new types ofwellness data that can be provided by the known source. For example, thenumber “2” is shown for Device 1, indicating the two new types of data(e.g., Calories burned and flights of stairs climbed) are available.

In some examples, process 3700 can further include detecting a selectionof a known source from the list of displayed sources. In response todetecting the selection of the known source, a list of types of wellnessdata that the known source can provide can be displayed. For example, asource from source list 3506 of interface 3500 can be received by a userselecting an option 3510 associated with the source. In response, aninterface similar or identical to interface 3600 can be displayed. Thedisplayed interface can include a list (e.g., list 3606) of known typesof data that the source can provide. In some examples, the list of typesof wellness data that the known source can provide can include aselectable option (e.g., options 3604, 3608, 3610, 3612, and 3614) foreach of the types of wellness data that the known source can provide toapprove or reject the associated type of wellness data.

In some examples, process 3700 can further include detecting a selectionof the selectable option for a type of wellness data that the knownsource can provide at the electronic device. In response to detectingthe selection of the selectable option, process 3700 can further includeapproving or rejecting the type of wellness data that the known sourcecan provide in accordance with the detected selection of the selectableoption. For example, user device 510 can accept or reject the types ofwellness data shown in interface 3600 based on the positions of theswitches of options 3604, 3608, 3610, 3612, and 3614.

It should be understood that the particular order in which theoperations in FIGS. 37A and 37B have been described is merely exemplaryand is not intended to indicate that the described order is the onlyorder in which the operations could be performed. One of ordinary skillin the art would recognize various ways to reorder the operationsdescribed herein. Additionally, it should be noted that details of otherprocesses described herein with respect to other processes describedherein (e.g., processes 800, 1500, 1700, 2000, 2600, or 4400) are alsoapplicable in an analogous manner to process 3700 described above withrespect to FIGS. 37A and 37B. For brevity, these details are notrepeated here.

Medical Identification Information

FIG. 38 illustrates one example lock screen interface 3800 that can bedisplayed by user device 510 while the user device is in a locked state.In some examples, the locked state can represent a state in which userdevice 510 restricts one or more functions from being performed. Forexample, user device 510 can prevent a user from running applications,changing settings, or the like, while in the locked state. In otherexamples, the locked state can represent a state in which user device510 additionally or alternatively prevents access at least a subset ofdata stored on the device. For example, user device 510 can prevent auser from viewing photos or videos, accessing documents, or the like,while in the locked state. In other examples, the locked state canrepresent a state in which user device 510 additionally or alternativelyrestricts communications from the electronic device. For example, userdevice 510 can prevent a user from sending SMS messages or emails, ormaking calls to non-emergency phone numbers.

As shown in FIG. 38, lock screen interface 3800 can include the currentdate and time. Lock screen interface 3800 can further be responsive touser input to allow a user to unlock the device. For example, a swipinggesture can cause user device 510 to display a numerical input pad toallow the user to enter a passcode to unlock the device. Lock screeninterface 3800 can further include emergency option 3802 for accessingemergency features of user device 510. For example, FIG. 39 illustratesan example emergency dialing interface 3900 that can be displayed inresponse to a selection of emergency option 3802. As shown, emergencydialing interface 3900 can include numerical input pad 3904 for allowinga temporary user to enter an emergency phone number to dial while thedevice is in the locked state. In some examples, user device 510 cancall a number entered using input pad 3904 if the entered number ispredefined phone number (e.g., 9-1-1). In some examples, the temporaryuser can be a first responder or other person that encounters theprimary user of the device when the primary user of the device is unableto operate user device 510 (e.g., because the primary user isunconscious or injured). Thus, emergency dialing interface 3900 allowsthe temporary user to place calls to predetermined emergency phonenumbers without requiring the temporary user to unlock user device 510.

Interface 3900 can further include Medical ID or emergency informationoption 3902 for viewing medical information associated with a user bythe temporary user. In this example, the user can be a primary user orowner of user device 510 that has customized the device by installingapplications and/or entering personal information to user device 510.Thus, Medical ID or emergency information option 3902 can be selected bythe temporary user to view emergency information associated with theprimary user without requiring the temporary user to unlock user device510.

For example, FIG. 40 illustrates an example emergency informationinterface 4000 that can be displayed in response to a selection ofMedical ID or emergency information option 3902 in interface 3900. Asshown, interface 4000 can include user information 4002 including theuser's name and birthdate. Interface 4000 can further include afree-form field 4004 that can be used to store and display a descriptionof any medical conditions that the user may have. Interface 4000 canfurther include a free-form field 4006 that can be used to store anddisplay any other relevant medical notes about the user. Interface 4000can further include free-form field 4008 that can be used to store anddisplay a description of any allergies or reactions that the user mayhave to drugs or any other substance. Interface 4000 can further includefree-form field 4010 that can be used to store and display a descriptionof any medications that the user may be taking or that the user mayrequire.

Interface 4000 can further include emergency contacts 4012. Emergencycontacts 4012 can include a list of one or more people that the user hasdesignated as being his/her emergency contact. Emergency contacts 4012can include a name of each emergency contact and a relationship betweenthe user and the emergency contact. For example, one entry for anemergency contact can include the name “Jane Smith” having arelationship with the user of “mother.” In some examples, emergencycontacts 4012 can further include contact information for the emergencycontact, such as a phone number, email address, or the like. In otherexamples, emergency contact 4012 can exclude contact information for theemergency contact, such as a phone number, email address, or the like.This can be done to protect the privacy of the emergency contact. Ineither example, user device 510 can allow a temporary user to select oneof the displayed emergency contacts to initiate communication with thatcontact (even if the phone number of the emergency contact is notdisplayed) while user device 510 remains in the locked state. Forexample, in response to a selection of one of the emergency contacts,user device 510 can initiate a phone call to the contact, send an SMSmessage to the contact, send an email to the emergency contact, or thelike, while the device remains in the locked state. In some examples,when user device 510 initiates a call to an emergency contact inresponse to a selection of that emergency contact, user device 510 canflag the call as being an emergency call. In some examples, emergencycalls can be accepted by a receiving device in any state of operation.For example, a call flagged as being an emergency call can cause thereceiving device to ring while in a do-not-disturb mode, a silent mode,or the like. Additionally, an indicator can be displayed on thereceiving device notifying the recipient that the call is an emergencycall.

In some examples, a primary user can create their medical identificationfrom the contact list of user device 510. For example, FIG. 41illustrates an example interface 4100 that can be displayed to displaythe user's contact list. As shown, interface 4100 can include a “CreateMedical ID” button 4102 for creating a medical identification. FIG. 42illustrates an example interface 4200 that can be displayed in responseto a selection of button 4102. As shown, interface 4200 includes a textdescription 4202 that can provide information about the medicalidentification, such as the purpose of the medical identification, theprivacy settings for information contained in the medicalidentification, and the like.

FIG. 43 illustrates an example interface 4300 that can be displayed inresponse to a user accepting or acknowledging the contents ofdescription 4202 in interface 4200. As shown, interface 4300 can includeuser information 4302 that can correspond to user information 4002 ininterface 4000. In some examples, this information can be auto-populatedby user device 510 based on information previously known about the user.In other examples, the user can enter this information manually.Interface 4300 can further include free-form text fields 4304, 4306,4308, and 4310 that can correspond to fields 4004, 4006, 4008, and 4010of interface 4000. Thus, information entered into fields 4304, 4306,4308, and 4310 can be displayed in fields 4004, 4006, 4008, and 4010 ofinterface 4000. Interface 4300 can further include contacts 4312 toallow a user to enter one or more emergency contacts. In some examples,the one or more emergency contacts can be selected from the user'scontact list on user device 510. In other examples, the one or moreemergency contacts can be entered manually by the user. In yet otherexamples, the emergency contact can be selected from the user's contactlist on user device 510 and additional information (e.g., relationshipinformation) can be manually added by the user. Interface 4300 canfurther include “Show Medical ID” option 4314 having selectable option4316. The position of the switch of option 4316 can be used to turn onor off the showing of the user's medical information while the device isin the locked state. For example, when moved to the right, as shown inFIG. 43, the switch of option 4316 can cause user device 510 to displayoption 3902 in the emergency dialing interface 3900 and to displayinterface 4000 in response to a selection of option 3902. However, whenmoved to the left, the switch of option 4316 can prevent user device 510from displaying option 3902 in the emergency dialing interface 3900 andcan prevent user device 510 from displaying interface 4000 in responseto a selection of option 3902.

FIG. 44 illustrates an exemplary process 4400 for displaying medicalinformation on a locked device. Process 4400 can be performed at anelectronic device (e.g., device 510) with a display. In some examples,the display can include a touch-sensitive display. In other examples,the display can be separate from a touch-sensitive surface. Some blocksof process 4400 can be combined and/or the order of some blocks can bechanged.

As described below, process 4400 provides a way for a temporary user toview medical information associated with a primary user or owner of anelectronic device while the device remains in a locked state. Process4400 also allows a temporary user to initiate communication with theprimary user's emergency contacts while the device remains in the lockedstate. This advantageously allows a temporary user that finds theprimary user (e.g., in a state in which the primary user is unable tooperate the electronic device or communicate) to assist the primary userin getting the appropriate medical care.

At block 4402, at an electronic device (e.g., user device 510) while theelectronic device is in a locked state, a request to display emergencyinformation about a user of the device can be detected. For example, therequest to display the emergency information can be received while anemergency dialing interface similar or identical to interface 3900 isbeing displayed, and the request can include a selection of an emergencyinformation option similar or identical to option 3902. The emergencyinformation about the user of the device can include the user's name,birthday, medical conditions, allergies and reactions, medications, andone or more emergency contacts of the user. As discussed above, the usercan be a primary user or owner of user device 510 that has customizedthe device by installing applications and/or entering personalinformation to user device 510. The request to display the medicalinformation can be made by a temporary user, such as a first responderor other person that encounters the primary user of the device when theprimary user of the device is unable to operate user device 510 (e.g.,because the primary user is unconscious or injured).

At block 4404, in response to detecting the request, an emergencyinformation interface comprising emergency information about the user ofthe device can be displayed without unlocking the device. For example,an interface similar or identical to interface 4000 can be displayed.

In some examples, the emergency information about the user can includeinformation associated with an emergency contact. The informationassociated with the emergency contact can include a name of theemergency contact and a relationship between the user and the emergencycontact. For example, information about an emergency contact can bedisplayed in a manner similar or identical to emergency contact 4012 ininterface 4000. One example emergency contact can include the contact'sname “Jane Smith,” and the relationship “mother” between the user andthe contact.

At block 4406, user device 510 can detect a request to communicate withan emergency contact while the electronic device is in the locked state.For example, a selection of a contact 4012 from interface 4000 can bedetected.

At block 4408, user device 510 can initiate communication with theemergency contact in response to detecting the request to communicate.In some examples, initiating communication with the emergency contactincludes sending an SMS message or email to the emergency contact. Inother examples, initiating communication with the emergency contact caninclude calling a phone number associated with the emergency contact. Insome examples, calling the phone number associated with the emergencycontact can include flagging the call to the phone number as anemergency call. In some examples, the phone number associated with theemergency contact can be included in the information associated with theemergency contact displayed within the emergency information interface(e.g., interface 4000). In other examples, the phone number associatedwith the emergency contact may not be included in the informationassociated with the emergency contact displayed within the emergencyinformation interface (e.g., interface 4000). However, a call or othercommunication can still be made to this emergency contact. This can bedone to protect the privacy of the emergency contact.

In some examples, process 4400 can include displaying an emergencydialing interface prior to displaying the emergency informationinterface. The emergency dialing interface can include a numerical inputpad and an emergency information option. For example, an emergencydialing interface similar or identical to interface 3900 can bedisplayed prior to displaying emergency information interface 4000. Theemergency dialing interface 3900 can include a numerical input padsimilar or identical to input pad 3904 and an emergency informationoption similar or identical to option 3902. In some examples, theemergency information interface (e.g., interface 4000) can be displayedin response to a selection of the emergency information option (e.g.,option 3902).

In some examples, process 4400 can further include detecting apredefined phone number entered using the numerical input pad while theelectronic device is in the locked state. In response to detecting thepredefined phone number, process 4400 can further include calling thepredefined phone number. For example, user device 510 can detect apredefined number (e.g., 9-1-1) entered in the numerical input pad(e.g., input pad 3904). In response to detecting the predefined phonenumber, user device 510 can call the predefined number while still inthe locked state. In some examples, calling the predefined phone numbercan include flagging the call to the predefined phone number as anemergency call.

In some examples, calls flagged as being emergency calls can be acceptedby a receiving electronic device in any state of operation. For example,a call flagged as being an emergency call can cause the receiving deviceto ring while in a do-not-disturb mode, a silent mode, or the like.Additionally, an indicator can be displayed on the receiving devicenotifying the recipient that the call is an emergency call.

In some examples, process 4400 can further include displaying a lockscreen interface comprising an emergency option prior to displaying theemergency dialing interface. For example, an interface similar oridentical to interface 3800 can be displayed having an emergency optionsimilar or identical to option 3802. The lock screen interface canfurther include one or more controls for unlocking the device. Forexample, a numerical input pad can be displayed to allow a user to entera passcode, or user device 510 can be configured to detect predefinedgestures to unlock the device. In these examples process 4400 canfurther include detecting a selection of the emergency option anddisplaying the emergency dialing interface in response to detecting theselection of the emergency option. For example, user device 510 candetect a selection of option 3802 and display interface 3900 in responseto detecting the selection of option 3802.

It should be understood that the particular order in which theoperations in FIG. 44 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other processes described herein (e.g.,processes 800, 1500, 1700, 2000, 2600, or 3700) are also applicable inan analogous manner to process 4400 described above with respect to FIG.44. For brevity, these details are not repeated here.

In some examples, the interfaces shown in FIGS. 21-22, 27-36, and 40-43can include menu bar 2150 for navigating between the various interfaces.For example, in response to a selection of “Dashboard” in menu 2150,interface 2100 or 2200 can be displayed. In response to a selection of“My Health” in menu 2150, interface 2700 can be displayed. In responseto a selection of “Medical ID” in menu 2150, interface 4300 can bedisplayed. In response to a selection of “Settings” in menu 2150,interface 3500 can be displayed.

One or more of the functions relating to aggregating and sharingwellness data can be performed by a system similar or identical tosystem 4500 shown in FIG. 45. System 4500 can include instructionsstored in a non-transitory computer readable storage medium, such asmemory 4504 or storage device 4502, and executed by processor 4506. Theinstructions can also be stored and/or transported within anynon-transitory computer readable storage medium for use by or inconnection with an instruction execution system, apparatus, or device,such as a computer-based system, processor-containing system, or othersystem that can fetch the instructions from the instruction executionsystem, apparatus, or device and execute the instructions. In thecontext of this document, a “non-transitory computer readable storagemedium” can be any medium that can contain or store the program for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer readable storage medium can include,but is not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus or device,a portable computer diskette (magnetic), a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory(EPROM) (magnetic), a portable optical disc such a CD, CD-R, CD-RW, DVD,DVD-R, or DVD-RW, or flash memory such as compact flash cards, secureddigital cards, USB memory devices, memory sticks, and the like.

The instructions can also be propagated within any transport medium foruse by or in connection with an instruction execution system, apparatus,or device, such as a computer-based system, processor-containing system,or other system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “transport medium” can be any mediumthat can communicate, propagate or transport the program for use by orin connection with the instruction execution system, apparatus, ordevice. The transport medium can include, but is not limited to, anelectronic, magnetic, optical, electromagnetic or infrared wired orwireless propagation medium.

In some examples, system 4500 can be included within user device 510 oruser server 514. Processor 4506 can be configured to perform processes700, 800, 1500, 1700, 2000, 2600, 3700, or 4400. It is to be understoodthat the system is not limited to the components and configuration ofFIG. 45, but can include other or additional components in multipleconfigurations according to various examples.

Electronic De Vice

In accordance with some examples, FIG. 46 shows a functional blockdiagram of an electronic device 4600 configured in accordance with theprinciples of the various described examples. The functional blocks ofthe device can be implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the variousdescribed examples. It is understood by persons of skill in the art thatthe functional blocks described in FIG. 46 can be combined or separatedinto sub-blocks to implement the principles of the various describedexamples. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein.

As shown in FIG. 46, electronic device 4600 can include a touchsensitive surface unit 4602 configured to receive touch input, and adisplay unit for displaying a user interface. Electronic device 4600 canfurther include a processing unit 4608 coupled to touch sensitivesurface unit 4602 and display unit 4608. In some examples, processingunit 4608 can include a graph displaying unit 4610, a user inputdetecting unit 4612, a first indication displaying unit 4614, a secondindication displaying unit 4616, and a detailed view displaying unit4618.

Processing unit 4608 can be configured to display (e.g., using graphdisplaying unit 4610) a graph comprising a first data-set representationof a first data set in which a first dependent variable varies as anindependent variable changes and a second data-set representation of asecond data set in which a second dependent variable varies as theindependent variable changes, wherein the first data-set representationis associated with a first range of vertical positions within the graphand the second data-set representation is associated with a second rangeof vertical positions within the graph. Processing unit 4608 can befurther configured to detect (e.g., using detecting unit 4612) a userinput at a respective location on the display. Processing unit 4608 canbe further configured to, in response to detecting the user input and inaccordance with a determination that the respective location is withinthe first range of vertical positions associated with the first data-setrepresentation, display (e.g., using first indication displaying unit4614) an indication that the first data-set representation has beenselected. Processing unit 4608 can be further configured to, in responseto detecting the user input and in accordance with a determination thatthe respective location is within the second range of vertical positionsassociated with the second data-set representation display (e.g., usingsecond indication displaying unit 4616) an indication that the seconddata-set representation has been selected.

In some examples, processing unit 4608 can be further configured todisplay (e.g., using graph displaying unit 4610) the first data-setrepresentation in the graph overlapping the second data-setrepresentation.

In some examples, the first data set comprises a first set of wellnessdata and the second data set comprises a second set of wellness data.

In some examples, the first range of vertical positions is uniquelyassociated with the first data-set representation, and the second rangeof vertical positions is uniquely associated with the second data-setrepresentation.

In some examples, the first data-set representation and the seconddata-set representation are colored-coded based on a type of data thatthey represent.

In some examples, processing unit 4608 can be further configured todisplay (e.g., using first indication displaying unit 4614) theindication that the first data-set representation has been selected bydisplaying, on the display, a marker overlaid on the first data-setrepresentation at a horizontal position corresponding to a horizontalposition of the respective location on the display.

In some examples, processing unit 4608 can be further configured todisplay (e.g., using second indication displaying unit 4616) theindication that the second data-set representation has been selected bydisplaying, on the display, a marker overlaid on the second data-setrepresentation at a horizontal position corresponding to a horizontalposition of the respective location on the display.

In some examples, processing unit 4608 can be further configured todisplay (e.g., using first indication displaying unit 4614) theindication that the first data-set representation has been selected bydisplaying, on the display, a numerical value of a first data entry ofthe first data set associated with a value of the independent variablecorresponding to a horizontal position of the respective location on thedisplay.

In some examples, processing unit 4608 can be further configured todisplay (e.g., using second indication displaying unit 4616) theindication that the second data-set representation has been selected bydisplaying, on the display, a numerical value of a second data entry ofthe second data set associated with a value of the independent variablecorresponding to a horizontal position of the respective location on thedisplay.

In some examples, the first data set or the second data set comprisesblood pressure data, and wherein the numerical value of the first dataentry or the second data entry comprises a high value for diastolicblood pressure, a low value for diastolic blood pressure, a high valuefor systolic blood pressure, and a low value for systolic bloodpressure.

In some examples, processing unit 4608 can be further configured togenerate (e.g., using graph displaying unit 4610) the first data-setrepresentation or the second data-set representation based on an averageof blood pressure values.

In some examples, the first data set or the second data set comprisesheart rate data, and the numerical value of the first data entry or thesecond data entry comprises a high value for heart rate and a low valuefor heart rate.

In some examples, the first data-set representation comprises a firstline in the graph, and processing unit 4608 can be further configured todisplay (e.g., using first indication displaying unit 4614) theindication that the first data-set representation has been selected byhighlighting an area below the first line.

In some examples, the second data-set representation comprises a secondline in the graph, and processing unit 4608 can be further configured todisplay (e.g., using first indication displaying unit 4614) theindication that the second data-set representation has been selected byhighlighting an area below the second line.

In some examples, processing unit 4608 can be further configured toexpand (e.g., using detecting unit 4614) the first range of verticalpositions within the graph based on a length of time that the user inputis detected while a vertical position of the respective location on thedisplay is within the first range of vertical positions, and to expand(e.g., using detecting unit 4614) the second range of vertical positionswithin the graph based on a length of time that the user input isdetected while the vertical position of the respective location on thedisplay is within the second range of vertical positions.

In some examples, the dependent variable for the first data set ismeasured in different units from the dependent variable for the seconddata set.

In some examples, a vertical scale for displaying the first data-setrepresentation is different from a vertical scale for displaying thesecond data-set representation.

In some examples, processing unit 4608 can be further configured todetermine (e.g., using graph displaying unit 4610) the vertical scalefor the first data-set representation based on the maximum and minimumvalues of the first dependent variable of the first data-setrepresentation that are to be displayed in the graph, and to determine(e.g., using graph displaying unit 4610) the vertical scale for thesecond data-set representation based on the maximum and minimum valuesof the second dependent variable of the second data-set representationthat are to be displayed in the graph.

In some examples, the vertical scale for the first data-setrepresentation of the plurality of sets of wellness data is defined by:a maximum vertical position within the graph corresponding to a firstmultiplying factor multiplied by the maximum value of the firstdependent variable of the first data-set representation that are to bedisplayed in the graph; and a minimum vertical position within the graphcorresponding to a second multiplying factor multiplied by the minimumvalue of the first dependent variable of the first data-setrepresentation that are to be displayed in the graph.

In some examples, the vertical scale for the second data-setrepresentation of the plurality of sets of wellness data is defined by:a maximum vertical position within the graph corresponding to a thirdmultiplying factor multiplied by the maximum value of the seconddependent variable of the second data-set representation that are to bedisplayed in the graph; and a minimum vertical position within the graphcorresponding to a fourth multiplying factor multiplied by the minimumvalue of the second dependent variable of the second data-setrepresentation that are to be displayed in the graph.

In some examples, processing unit 4608 can be further configured todetect (e.g., using detecting unit 4612) a detailed-view input anddisplay (e.g., using detailed view displaying unit 4618) a detailed viewof the first data set and the second data set in response to detectingthe detailed-view input, wherein the detailed view comprises a firstpartition associated with the first data set and a second partitionassociated with the second data set.

In some examples, processing unit 4608 can be further configured todetect (e.g., using detecting unit 4612) the detailed-view input bydetecting a change in orientation of the electronic device whiledisplaying the graph.

In some examples, processing unit 4608 can be further configured todetect (e.g., using detecting unit 4612) a request to scroll thedetailed view and scroll (e.g., using detailed view displaying unit4618) the detailed view in response to detecting the request to scrollthe detailed view.

In some examples, the first partition comprises a first graphrepresentation of the first data set, and the second partition comprisesa second graph representation of the second data set.

In some examples, the first graph representation is non-overlapping withthe second graph representation.

In some examples, the first partition is displayed in a color matching acolor of the first data-set representation, and the second partition isdisplayed in a color matching a color of the second data-setrepresentation.

In some examples, the first partition is displayed in a color matching acolor of the first data-set representation, and the second partition isdisplayed in a color matching a color of the second data-setrepresentation.

In some examples, processing unit 4608 can be further configured todetect (e.g., using detecting unit 4612) a request to reorder the firstpartition and the second partition and to reorder (e.g., using detailedview displaying unit 4618) the first partition and the second partitionwithin the detailed view in response to detecting the request to reorderthe first partition and the second partition.

In some examples, processing unit 4608 can be further configured todetect (e.g., using detecting unit 4612) graph-view input and display(e.g., using graph displaying unit 4610) the graph comprising the firstdata-set representation of the first data set and the second data-setrepresentation of the second data set in response to detecting thegraph-view input.

In accordance with some examples, FIG. 47 shows a functional blockdiagram of an electronic device 4700 configured in accordance with theprinciples of the various described examples. The functional blocks ofthe device can be implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the variousdescribed examples. It is understood by persons of skill in the art thatthe functional blocks described in FIG. 47 can be combined or separatedinto sub-blocks to implement the principles of the various describedexamples. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein.

As shown in FIG. 47, electronic device 4700 can include a touchsensitive surface unit 4702 configured to receive touch input, and adisplay unit for displaying a user interface. Electronic device 4700 canfurther include a processing unit 4708 coupled to touch sensitivesurface unit 4702 and display unit 4708. In some examples, processingunit 4708 can include a detecting unit 4710, a displaying unit 4712, acommunication unit 4714, a displaying unit 4716, and a displaying unit4718.

Processing unit 4708 can be configured to detect (e.g., using detectingunit 4710) a request to display emergency information about a user ofthe device while the electronic device is in a locked state. Processingunit 4708 can be further configured to display (e.g., using displayingunit 4712), while the electronic device is in the locked state, anemergency information interface comprising emergency information aboutthe user of the device without unlocking the device in response todetecting the request.

In some examples, processing unit 4708 can be configured to restrict oneor more functions of the electronic device from being used whileelectronic device 4700 is in the locked state.

In some examples, processing unit 4708 can be configured to preventaccess to at least a subset of data stored on the electronic devicewhile electronic device 4700 is in the locked state.

In some examples, processing unit 4708 can be configured to restrictcommunications from the electronic device while electronic device 4700is in the locked state.

In some examples, the emergency information about the user comprisesinformation associated with an emergency contact, and the informationassociated with the emergency contacts comprises a name of the emergencycontact and a relationship between the user and the emergency contact.

In some examples, processing unit 4708 can be further configured todetect (e.g., using detecting unit 4710) a request to communicate whilethe electronic device is in the locked state and to initiate (e.g.,using communication unit 4714) communication with the emergency contactin response to detecting the request to communicate.

In some examples, initiating communication with the emergency contactcomprises sending an SMS message or email to the emergency contact.

In some examples, initiating communication with the emergency contactcomprises calling a phone number associated with the emergency contact.In some examples, calling the phone number associated with the emergencycontact comprises flagging the call to the phone number as an emergencycall.

In some examples, the information associated with the emergency contactsfurther comprises the phone number associated with the emergencycontact.

In some examples, the information associated with the emergency contactsexcludes the phone number associated with the emergency contact.

In some examples, processing unit 4708 can be further configured todisplay (e.g., using displaying unit 4716), prior to displaying theemergency information interface an emergency dialing interfacecomprising a numerical input pad and an emergency information option.Processing unit 4708 can be further configured to detect (e.g., usingdetecting unit 4712), while displaying the emergency dialing interface,a selection of the emergency information option and to display (e.g.,using displaying unit 4712) the emergency information interface inresponse to detecting selection of the emergency information option.

In some examples, processing unit 4708 can be further configured todetect (e.g., using detecting unit 4710) a predefined phone numberentered using the numerical input pad while the electronic device is inthe locked state and to call (e.g., using communication unit 4714) thepredefined phone number in response to detecting the predefined phonenumber. In some examples, calling the predefined phone number comprisesflagging the call to the predefined phone number as an emergency call.In some examples, calls flagged as an emergency call are to be acceptedby a receiving electronic device in any state of operation.

In some examples, processing unit 4708 can be further configured todisplay (e.g., using displaying unit 4718), prior to displaying theemergency dialing interface, a lock screen interface comprising anemergency option and to detect (e.g., using detecting unit 4710) aselection of the emergency option. Processing unit 4708 can be furtherconfigured to display (e.g., using displaying unit 4716) and theemergency dialing interface in response to detecting the selection ofthe emergency option.

In some examples, the emergency information about the user comprises oneor more of: the user's name, birthday, medical conditions, allergies andreactions, medications, and one or more emergency contacts of the user.

In accordance with some examples, FIG. 48 shows a functional blockdiagram of an electronic device 4800 configured in accordance with theprinciples of the various described examples. The functional blocks ofthe device can be implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the variousdescribed examples. It is understood by persons of skill in the art thatthe functional blocks described in FIG. 48 can be combined or separatedinto sub-blocks to implement the principles of the various describedexamples. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein.

As shown in FIG. 48, electronic device 4800 can include a touchsensitive surface unit 4802 configured to receive touch input, and adisplay unit for displaying a user interface. Electronic device 4800 canfurther include a processing unit 4808 coupled to touch sensitivesurface unit 4802 and display unit 4808. In some examples, processingunit 4808 can include a source receiving unit 4810, a destinationreceiving unit 4812, a first identifying unit 4814, a second identifyingunit 4816, a prioritizing unit 4818, a displaying unit 4820, a detectingunit 4822, and a receiving unit 4824.

Processing unit 4808 can be configured to receive (e.g., using sourcereceiving unit 4810), from a user, information identifying a pluralityof approved sources of wellness data, wherein the informationidentifying the plurality of approved sources identifies one or moretypes of wellness data that are approved to be received from theplurality of approved sources and stored in a wellness database.Processing unit 4808 can be further configured to receive (e.g., usingdestination receiving unit 4812), from the user, information identifyinga plurality of approved destinations of wellness data, wherein theinformation identifying the plurality of approved destinationsidentifies one or more types of wellness data that are approved to beaccessed from the wellness database by the plurality of approveddestinations of wellness data.

In some examples, the plurality of approved sources comprise anelectronic device or software application.

In some examples, the plurality of approved destinations comprise anelectronic device or software application.

In some examples, the plurality of approved sources are ranked amongsteach other.

In some examples, processing unit 4808 can be further configured toidentify (e.g., using first identifying unit 4814) a first wellness dataentry in the wellness database that was received from a first approvedsource of the plurality of approved sources, the first wellness dataentry comprising a first wellness data type and a first timestamp and toidentify (e.g., using second identifying unit 4816) a second wellnessdata entry in the wellness database that was received from a secondapproved source of the plurality of approved sources, the secondwellness data entry comprising a second wellness data type and a secondtimestamp, wherein the first wellness data type and the second wellnessdata type are the same, and wherein the first timestamp is within athreshold length of time from the second timestamp.

In some examples, the first approved source has been identified by theuser as being preferred over the second approved source, and whereinprocessing unit 4808 can be further configured to use (e.g., usingprioritizing unit 4818) the first wellness data entry instead of usingthe second wellness data entry.

In some examples, the first approved source has been identified by theuser as being preferred over the second approved source, and processingunit 4808 can be further configured to prioritize (e.g., usingprioritizing unit 4818) the first wellness data entry over the secondwellness data entry.

In some examples, in accordance with a determination that the firstwellness data entry is prioritized over the second wellness data entry,processing unit 4808 can be further configured to use (e.g., usingprioritizing unit 4818) the first wellness data entry instead of usingthe second wellness data entry.

In some examples, the second approved source has been identified by theuser as being preferred over the first approved source, and processingunit 4808 can be further configured to prioritize (e.g., usingprioritizing unit 4818) the second wellness data entry over the firstwellness data entry.

In some examples, in accordance with a determination that the secondwellness data entry is prioritized over the first wellness data entry,processing unit 4808 can be further configured to use (e.g., usingprioritizing unit 4818) the second wellness data entry instead of usingthe first wellness data entry.

In some examples, processing unit 4808 can be further configured todisplay (e.g., using displaying unit 4820) a plurality of categories ofwellness data stored in the wellness database.

In some examples, processing unit 4808 can be further configured todetect (e.g., using detecting unit 4822) a selection of a category ofwellness data from the displayed plurality of categories of wellnessdata and to display (e.g., using displaying unit 4820) one or moresub-categories of the category of wellness data in response to detectingthe selection of the category of wellness data.

In some examples, processing unit 4808 can be further configured todetect (e.g., using detecting unit 4822) a selection of a sub-categoryfrom the displayed one or more sub-categories and to display (e.g.,using displaying unit 4820) a detailed view of the sub-category inresponse to detecting the selection of the sub-category.

In some examples, the detailed view of the sub-category comprises agraph representation of the sub-category of wellness data over time anda numerical daily value of the sub-category of wellness data.

In some examples, the detailed view of the sub-category furthercomprises an input field for entering a wellness data entry, and whereinprocessing unit 4808 can be further configured to receive (e.g., usingreceiving unit 4824) a wellness data entry to be stored in the wellnessdatabase that was input into the input field.

In some examples, the detailed view of the sub-category furthercomprises a textual description of the sub-category.

In some examples, the detailed view of the sub-category furthercomprises an option to view wellness data entries corresponding to thesub-category, and processing unit 4808 can be further configured todisplay (e.g., using displaying unit 4820) a plurality of wellness dataentries corresponding to the sub-category stored in the wellnessdatabase.

In some examples, each of the plurality of wellness data entriescomprises a numerical value of the data entry, a timestamp, and anidentification of a source of the data entry.

In some examples, the detailed view of the sub-category furthercomprises an option to share wellness data, and processing unit 4808 canbe further configured to reorder (e.g., using displaying unit 4820) thedisplayed plurality of approved sources in accordance with the detectedrequest to reorder the displayed plurality of approved sources inresponse to detecting the request to reorder the displayed plurality ofapproved sources.

In some examples, the data sharing interface further comprises optionsto add an approved destination to the plurality of approved destinationsand to remove an approved destination from the plurality of approveddestinations.

In some examples, processing unit 4808 can be further configured toreceive (e.g., using receiving unit 4824) a search query and to display(e.g., using displaying unit 4820) one or more sub-categories of theplurality of categories that match the search query, wherein thedisplayed one or more sub-categories that match the search query arecolor-coded based on their respective categories.

In some examples, processing unit 4808 can be further configured todisplay (e.g., using displaying unit 4820) a source interface comprisinga list of known sources.

In some examples, the source interface further comprises a numericalindicator associated a known source of the known sources that representsa number of new types of wellness data that can be provided by the knownsource.

In some examples, processing unit 4808 can be further configured todetect (e.g., using detecting unit 4822) a selection of a known sourcefrom the displayed list of known sources and to display (e.g., usingdisplaying unit 4820) a list of types of wellness data that the knownsource can provide in response to detecting the selection of the knownsource.

In some examples, the list of types of wellness data that the knownsource can provide comprises a selectable option for each of the typesof wellness data that the known source can provide to approve or rejectthe associated type of wellness data.

In some examples, processing unit 4808 can be further configured todetect (e.g., using detecting unit 4822) a selection of the selectableoption for a type of wellness data that the known source can provide andto approve or reject the type of wellness data that the known source canprovide in accordance with the detected selection of the selectableoption in response to detecting the selection of the selectable option

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data can include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplates examplesin which users selectively block the use of, or access to, personalinformation data. That is, the present disclosure contemplates thathardware and/or software elements can be provided to prevent or blockaccess to such personal information data. For example, in the case ofadvertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedexamples, the present disclosure also contemplates that the variousexamples can also be implemented without the need for accessing suchpersonal information data. That is, the various examples of the presenttechnology are not rendered inoperable due to the lack of all or aportion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

Although examples have been fully described with reference to theaccompanying drawings, it is to be noted that various changes andmodifications will become apparent to those skilled in the art. Suchchanges and modifications are to be understood as being included withinthe scope of the various examples as defined by the appended claims.

What is claimed is:
 1. A non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: determining an order in which todisplay a plurality of partitions, wherein a first partition of theplurality of partitions is associated with a first type of a pluralityof types of wellness data, and wherein a second partition of theplurality of partitions is associated with a second type of theplurality of types of wellness data different from the first type;displaying an aggregated view of the plurality of types of wellnessdata, wherein the aggregated view comprises a list of the plurality ofpartitions ordered according to the determined order and wherein thedisplay of each partition of the plurality of partitions, in theaggregated view, includes displaying a first portion of the associatedtype of wellness data that includes an identifier of the associated typeof wellness data; dynamically re-ordering the display of the pluralityof partitions; receiving a selection of a partition of the plurality ofpartitions; and in response to receiving the selection: ceasing todisplay the plurality of partitions; displaying an expanded view of theselected partition of the plurality of partitions, wherein the expandedview of the selected partition includes display of the first portion anda second portion of the associated type of wellness data.
 2. Thenon-transitory computer-readable storage medium of claim 1, wherein theexpanded view comprises a larger view of the selected partition of theplurality of partitions.
 3. The non-transitory computer-readable storagemedium of claim 2, wherein the first portion of the associated type ofwellness data comprises a most recent value of the associated type ofwellness data, and wherein the second portion of the associated type ofwellness data comprises a representation of the associated type ofwellness data over time.
 4. The non-transitory computer-readable storagemedium of claim 1, wherein displaying the expanded view of the selectedpartition comprises displaying a collapsed set of partitionsrepresenting partitions of the plurality of partitions that were notselected.
 5. The non-transitory computer-readable storage medium ofclaim 1, wherein the plurality of partitions are ordered within thedisplay based on a frequency of use of an associated type of wellnessdata, a time of most recently added value of the associated type ofwellness data, or a time of day.
 6. The non-transitory computer-readablestorage medium of claim 1, wherein the expanded view of the selectedpartition comprises a selectable element to share the wellness dataassociated with the partition through email or text message.
 7. Thenon-transitory computer-readable storage medium of claim 1, wherein theplurality of types of wellness data comprises weight data, blood sugardata, blood pressure data, activity data, or heart rate data.
 8. Thenon-transitory computer-readable storage medium of claim 1, wherein atleast one of the plurality of types of wellness data is generated fromsensor data obtained from a plurality of sensors.
 9. The non-transitorycomputer-readable storage medium of claim 1, wherein the expanded viewcomprises a graph of the associated type of wellness data, and whereinthe graph comprises segments generated from wellness data obtained fromdifferent sensors.
 10. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: determining an order in which to display aplurality of partitions, wherein a first partition of the plurality ofpartitions is associated with a first type of a plurality of types ofwellness data, and wherein a second partition of the plurality ofpartitions is associated with a second type of the plurality of types ofwellness data different from the first type; displaying an aggregatedview of the plurality of types of wellness data, wherein the aggregatedview comprises a list of the plurality of partitions ordered accordingto the determined order and wherein the display of each partition of theplurality of partitions, in the aggregated view, includes displaying ofa first portion of the associated type of wellness data that includes anidentifier of the associated type of wellness data; dynamicallyre-ordering the display of the plurality of partitions; receiving aselection of a partition of the plurality of partitions; and in responseto receiving the selection: ceasing to display the plurality ofpartitions; displaying an expanded view of the selected partition of theplurality of partitions, wherein the expanded view of the selectedpartition includes display of the first portion and a second portion ofthe associated type of wellness data.
 11. The electronic device of claim10, wherein the expanded view comprises a larger view of the selectedpartition of the plurality of partitions.
 12. The electronic device ofclaim 11, wherein the first portion of the associated type of wellnessdata comprises a most recent value of the associated type of wellnessdata, and wherein the second portion of the associated type of wellnessdata comprises a representation of the associated type of wellness dataover time.
 13. The electronic device of claim 10, wherein displaying theexpanded view of the selected partition comprises displaying a collapsedset of partitions representing partitions of the plurality of partitionsthat were not selected.
 14. The electronic device of claim 10, whereinthe plurality of partitions are ordered within the display based on afrequency of use of an associated type of wellness data, a time of mostrecently added value of the associated type of wellness data, or a timeof day.
 15. The electronic device of claim 10, wherein the expanded viewof the selected partition comprises a selectable element to share thewellness data associated with the partition through email or textmessage.
 16. The electronic device of claim 10, wherein the plurality oftypes of wellness data comprises weight data, blood sugar data, bloodpressure data, activity data, or heart rate data.
 17. The electronicdevice of claim 10, wherein at least one of the plurality of types ofwellness data is generated from sensor data obtained from a plurality ofsensors.
 18. The electronic device of claim 10, wherein the expandedview comprises a graph of the associated type of wellness data, andwherein the graph comprises segments generated from wellness dataobtained from different sensors.
 19. A method for presenting wellnessdata, the method comprising: determining an order in which to display aplurality of partitions, wherein a first partition of the plurality ofpartitions is associated with a first type of a plurality of types ofwellness data, and wherein a second partition of the plurality ofpartitions is associated with a second type of the plurality of types ofwellness data different from the first type; displaying an aggregatedview of the plurality of types of wellness data, wherein the aggregatedview comprises a list of the plurality of partitions ordered accordingto the determined order and wherein the display of each partition of theplurality of partitions, in the aggregated view, includes displaying ofa first portion of the associated type of wellness data that includes anidentifier of the associated type of wellness data; dynamicallyre-ordering the display of the plurality of partitions; receiving aselection of a partition of the plurality of partitions; and in responseto receiving the selection: ceasing to display the plurality ofpartitions; displaying an expanded view of the selected partition of theplurality of partitions, wherein the expanded view of the selectedpartition includes display of the first portion and a second portion ofthe associated type of wellness data.
 20. The method of claim 19,wherein the expanded view comprises a larger view of the selectedpartition of the plurality of partitions.
 21. The method of claim 20,wherein the first portion of the associated type of wellness datacomprises a most recent value of the associated type of wellness data,and wherein the second portion of the associated type of wellness datacomprises a representation of the associated type of wellness data overtime.
 22. The method of claim 19, wherein displaying the expanded viewof the selected partition comprises displaying a collapsed set ofpartitions representing partitions of the plurality of partitions thatwere not selected.
 23. The method of claim 19, wherein the plurality ofpartitions are ordered within the display based on a frequency of use ofan associated type of wellness data, a time of most recently added valueof the associated type of wellness data, or a time of day.
 24. Themethod of claim 19, wherein the expanded view of the selected partitioncomprises a selectable element to share the wellness data associatedwith the partition through email or text message.
 25. The method ofclaim 19, wherein the plurality of types of wellness data comprisesweight data, blood sugar data, blood pressure data, activity data, orheart rate data.
 26. The method of claim 19, wherein at least one of theplurality of types of wellness data is generated from sensor dataobtained from a plurality of sensors.
 27. The method of claim 19,wherein the expanded view comprises a graph of the associated type ofwellness data, and wherein the graph comprises segments generated fromwellness data obtained from different sensors.
 28. The non-transitorycomputer-readable storage medium of claim 1, wherein a partition of theplurality of partitions is a user-generated partition.
 29. Thenon-transitory computer-readable storage medium of claim 1, wherein theplurality of partitions has the appearance of a plurality of cardsdisplayed in a stack.
 30. The electronic device of claim 10, wherein apartition of the plurality of partitions is a user-generated partition.31. The electronic device of claim 10, wherein the plurality ofpartitions has the appearance of a plurality of cards displayed in astack.
 32. The method of claim 19, wherein a partition of the pluralityof partitions is a user-generated partition.
 33. The method of claim 19,wherein the plurality of partitions has the appearance of a plurality ofcards displayed in a stack.